fix(#975): Fix daily build (#1013)

* fix#975): Fix daily build

.github/scripts/muffet.sh

@@ -26,8 +26,9 @@ muffet http://localhost:1313 \
   --exclude "https://github\.com/medic/cht-core/issues/new.*" \
   --exclude "https://github\.com/medic/cht-docs/commit.*" \
   --exclude "https://github\.com/medic/cht-core/commit.*" \
-  --exclude "https://github\.com/medic/cht-docs/edit/master/.*" \
+  --exclude "https://github\.com/medic/cht-docs/edit/main/.*" \
   --exclude "http[s]*://localhost[8443|5984]*" \
+  --exclude "http[s]*://*.my.local-ip.co*" \
   --exclude "http[s]*://cht\.domain\.com.*" \
   --exclude "http[s]*://127\.0\.0*" \
   --exclude "https://docs.google.com/spreadsheets/d/12345ABCDEF/.*"

.github/workflows/ci.yml

@@ -60,7 +60,7 @@ jobs:
         uses: rtCamp/[email protected]
         env:
           SLACK_WEBHOOK: '${{ secrets.SLACK_WEB_HOOK }}'
-          SLACK_CHANNEL: '#cht-squad-docs'
+          SLACK_CHANNEL: '#cht-doc-site'
           SLACK_COLOR: '#3278BD'
           SLACK_ICON: ":flappingphone:"
           SLACK_MESSAGE: 'Deploy Failed'

.github/workflows/daily.yml

@@ -12,7 +12,7 @@ on:
     # runs at 3:15am every day
     - cron:  '15 3 * * *'
 
-name: Test site and push live if we're on main branch
+name: Test site for broken links
 jobs:
   BuildLinkCheckPushLive:
     name:
@@ -51,7 +51,7 @@ jobs:
       - name: All Branches - Serve Hugo site
         run: |
           hugo server&
-          sleep 5
+          sleep 30
 
       - name: All Branches - Run Muffet link checker
         shell: bash
@@ -62,7 +62,7 @@ jobs:
         uses: rtCamp/[email protected]
         env:
           SLACK_WEBHOOK: '${{ secrets.SLACK_WEB_HOOK }}'
-          SLACK_CHANNEL: '#cht-squad-docs'
+          SLACK_CHANNEL: '#cht-doc-site'
           SLACK_COLOR: '#3278BD'
           SLACK_ICON: ":flappingphone:"
           SLACK_MESSAGE: 'Broken Links Found'

content/en/apps/guides/privacy/policy.md

@@ -16,6 +16,7 @@ This policy is reviewed and updated periodically by our Responsible Data Working
 If you have any questions, please reach out to our Data Protection Officer at [email protected]. 
 
 ## Table of Contents
+- [Table of Contents](#table-of-contents)
 - [Our responsible data promise](#our-responsible-data-promise)
 - [Compliance with applicable data regulations and policies](#compliance-with-applicable-data-regulations-and-policies)
 - [Data and protected health information](#data-and-protected-health-information)
@@ -24,7 +25,7 @@ If you have any questions, please reach out to our Data Protection Officer at su
 - [Security practices](#security-practices)
   - [Technology security overview](#technology-security-overview)
   - [Security training for our Partners](#security-training-for-our-partners)
-- [Inquiries with Medic’s Data Protection Officer](#inquiries-with-medic-mobiles-data-protection-officer)
+- [Inquiries with Medic’s Data Protection Officer](#inquiries-with-medics-data-protection-officer)
 
 
 

content/en/apps/tutorials/application-tests.md

@@ -317,7 +317,7 @@ According to the task configuration, these conditions need to be met for the ass
 2. The `contact_type` of the user's parent is: `chw_area`
 3. The current time is between the start and end dates of the task event.
 
-When testing with harness, the conditions 1 and 2 above can be set in the `harness.defaults.json` file. See the lines [31](#harness-defaults-json-31) and [26]((#harness-defaults-json-26)) respectively in the sample file further below.
+When testing with harness, the conditions 1 and 2 above can be set in the `harness.defaults.json` file. See the lines [31](#harness-defaults-json-31) and [26](#harness-defaults-json-26) respectively in the sample file further below.
 
 For the condition 3, let's look at the task event window in the task definition. As mentioned in the earlier tutorial, the task event is:
 - Due 7 days after the contact’s creation date.

content/en/contribute/docs/workflow.md

@@ -12,7 +12,7 @@ Anyone can contribute to CHT documentation by opening an issue in the [`cht-docs
 
 ### Basics
 
-* It is helpful to be comfortable with [git](https://git-scm.com/doc/ext) and [GitHub](https://lab.github.com/) to contribute to the CHT community.
+* It is helpful to be comfortable with [git](https://git-scm.com/doc/ext) and [GitHub](https://github.com/) to contribute to the CHT community.
 * The documentation source is in [GitHub](https://github.com/medic/cht-docs). The content pages are in the `/content/en/` directory.
 * Documentation is written in [Markdown](https://www.markdownguide.org/). 
 * The CHT site build uses [Hugo](https://gohugo.io/). You can also setup a [local clone](https://github.com/medic/cht-docs/blob/main/README.md).