fix(#1757): fix 404s

content/en/building/interoperability/ltfu.md

@@ -52,7 +52,7 @@ See the [OpenHIM guide]({{< ref "building/interoperability/openhim" >}}) for ins
     1. **HTTP Request** - To trigger the LTFU process for the newly created patient, you need to create a `ServiceRequest`. You can refer to the API documentation available [here](#servicerequest-resource) to learn how to create a `ServiceRequest`. Replace the `requester.reference` and the `subject.reference` with the `Organization` and `Patient` identifiers respectively. Once the `ServiceRequest` is received by the mediator, it will initiate the LTFU workflow for the patient, which includes reminders for follow-up appointments and check-ins. 
 
     1. **HTTP Request** - Verify that the `ServiceRequest` was successful in both OpenHIM Mediator & FHIR Resource. Navigate to the `Transaction Log` in the Admin Console. You should see three successful API calls, as in the image below:
-       ![](/docs/images/instance-service-request.png)
+       ![](./instance-service-request.png)
 
 4.  Handle LTFU Task
 
@@ -292,7 +292,7 @@ The `Encounter` resource is an essential part of the LTFU workflow, which is aut
 
 **ENCOUNTER_IDENTIFIER:** An identifier for the encounter that can be used when querying the FHIR database in the future. Ideally, it should point to a document on the source system (CHT) that represents this encounter.
 
-> NOTE: The `ENCOUNTER_IDENTIFIER` should be the same as the `PATIENT_IDENTIFIER`. The FHIR Subscription won't be resolved properly if they don't match. Updating an existing `Encounter` will also trigger pending `Subscription` that matches the `Encounter` document, which is one of the downsides of using this method. You can learn more about it by visiting [Official FHIR Subscription Resource Scope](https://fhir-ru.github.io/subscription.html#scope).
+> NOTE: The `ENCOUNTER_IDENTIFIER` should be the same as the `PATIENT_IDENTIFIER`. The FHIR Subscription won't be resolved properly if they don't match. Updating an existing `Encounter` will also trigger pending `Subscription` that matches the `Encounter` document, which is one of the downsides of using this method. You can learn more about it by visiting [Official FHIR Subscription Resource Scope](https://build.fhir.org/subscription.html#scope).
 
 
 ##### Request

content/en/design/user-experience-research/focus-group-discussions.md

@@ -19,7 +19,7 @@ Focus group discussions are a quick and convenient way to collect data from seve
     4. Location
     5. Mobile devices
 
-Here is a [focused group discussion template](https://docs.google.com/document/d/17DISQpIr8EbkFaSBMHZEXLwOrhzIxd1JmSZbMFWjqFo/edit?tab=t.0).
+Here is a [focused group discussion template]({{< ref "template" >}})
 
 ## Recruiting
 

content/en/design/user-experience-research/generative-template.md

@@ -0,0 +1,58 @@
+---
+title: "Generative Interview Guide"
+linkTitle: "Generative Interview Guide"
+---
+
+## Remember
+* Be warm, but professional.
+* Record audio when possible.
+* Sample real experiences, don’t ask for opinions (ex. Tell me about the last time you did XYZ).
+* No leading questions or examples of answers.
+* Silence is OK – give participants time to think about the question.
+* If the participant doesn’t understand the question, take a moment to rephrase it. Think about the insight you are trying to uncover.
+* Avoid becoming the expert. Even if the participant is doing something incorrectly, don’t correct them. Starting to correct them will also negatively change the dynamic of the interview.
+
+## Mission
+_Why are you doing this research? This is your North Star reminder of how this session will help your initiative forward_
+
+Sampling unbiased CHW experiences with the CHT to help understand how to improve their user experience
+
+## Learning objectives
+_In the discovery phase, your objectives likely include better understanding user context and pain. You might want to learn what tools or services they are currently using to solve their existing pains, and to test your hypothesis. List these objectives here so you can refer to them._
+
+To learn about, in as much detail as possible, the last time a CHW used the CHT
+
+## Script
+
+### Intro
+
+* Introduce yourself. Briefly explain your role and why you are talking to users. 
+* Talk about what will happen in the session, how long it might last, the sorts of questions you’ll ask them. 
+* Explain no right or wrong answers; it’s their experience that matters. 
+* Let them know there will be time for questions at the end. 
+* Explain why we record interviews and ask for permission.
+
+
+### Interview questions
+1. Please tell me about the last time you used the CHT in as much detail as possible
+
+
+#### Probe further to understand
+
+* How often do they open their app, and why (ex. What is their schedule)? 
+* When do they decide to visit a household, and how do they prioritize? 
+* What stood out as easy to do with the app? 
+* What was difficult? 
+* How long did their session take? 
+* Did they use any other tools to do their work? 
+* Who else was present, if anyone? 
+* What did they do before and after? 
+* Overview of all services provided (not just health related) for their communities 
+   * Tools that currently support this 
+   * Things they manage by memory
+
+
+### Conclusion
+* Thank them for their time
+* Let them know their feedback is important to improve the app for all CHWs
+

content/en/design/user-experience-research/scoped.md

@@ -0,0 +1,51 @@
+---
+title: "Scoped Interview Guide"
+linkTitle: "Scoped Interview Guide"
+---
+
+## Remember
+* Be warm, but professional. 
+* Record audio when possible. 
+* Sample real experiences, don’t ask for opinions (ex. Tell me about the last time you did XYZ). 
+* No leading questions or examples of answers. 
+* Silence is OK – give participants time to think about the question. 
+* If the participant doesn’t understand the question, take a moment to rephrase it. Think about the insight you are trying to uncover. 
+* Avoid becoming the expert. Even if the participant is doing something incorrectly, don’t correct them. Starting to correct them will also negatively change the dynamic of the interview.
+
+
+## Mission
+Why are you doing this research? This is your North Star reminder of how this session will help your initiative forward
+
+Sampling unbiased Supervisors’ experience with [a new feature]
+
+
+## Learning objectives
+In the discovery phase, your objectives likely include better understanding user context and pain. You might want to learn what tools or services they are currently using to solve their existing pains, and to test your hypothesis. List these objectives here so you can refer to them.
+
+To assess the impact and usability of [a new feature] and any challenges or opportunities for improvement
+
+## Script
+
+### Intro
+* Introduce yourself. Briefly explain your role and why you are talking to users.
+* Talk about what will happen in the session, how long it might last, the sorts of questions you’ll ask them.
+* Explain no right or wrong answers; it’s their experience that matters.
+* Let them know there will be time for questions at the end.
+* Explain why we record interviews and ask for permission.
+
+### Interview questions
+
+Assess the impact and usability of the [new feature]
+1. How do you currently [complete the function of the feature]?
+2. How long does that take?
+3. What is easy to do?
+4. What is difficult to do?
+5. How often do you use it?
+
+Assess challenges and opportunities for improvement of the [new feature]
+1. Did you encounter any difficulties when using the feature?
+2. Was it easy or difficult to learn how to use?
+
+### Conclusion
+* Thank them for their time
+* Let them know their feedback is important to improve the app for all CHWs

content/en/design/user-experience-research/template.md

@@ -0,0 +1,48 @@
+---
+title: "Focused Group Discussion Template"
+linkTitle: "Focused Group Discussion Template"
+---
+
+## Remember
+* Be warm, but professional.
+* Record audio when possible.
+* Sample real experiences, don’t ask for opinions (ex. Tell me about the last time you did XYZ).
+* No leading questions or examples of answers.
+* Silence is OK – give participants time to think about the question.
+* If the participant doesn’t understand the question, take a moment to rephrase it. Think about the insight you are trying to uncover.
+* Avoid becoming the expert. Even if the participant is doing something incorrectly, don’t correct them. Starting to correct them will also negatively change the dynamic of the interview.
+
+## Mission
+Why are you doing this research? This is your North Star reminder of how this session will help your initiative forward
+
+To learn more about CHWs’ thoughts and opinions on a [specific topic]
+
+## Learning objectives
+In the discovery phase, your objectives likely include better understanding user context and pain. You might want to learn what tools or services they are currently using to solve their existing pains, and to test your hypothesis. List these objectives here so you can refer to them.
+
+What do CHWs think about [XYZ]?
+
+## Script
+
+### Intro
+
+* Introduce yourself. Briefly explain your role and why you are talking to users.
+* Talk about what will happen in the session, how long it might last, the sorts of questions you’ll ask them.
+* Have the group introduce themselves.
+* Explain no right or wrong answers; it’s their experience that matters.
+* Let them know there will be time for questions at the end.
+* Explain why we record interviews and ask for permission.
+
+### Discussion topics
+1. When you think of [the topic], what comes to mind?
+2. How often do you deal with [the topic]?
+3. What do you like or dislike most about [the topic]?
+4. How does it compare to [XYZ]?
+5. Does it meet the needs of its function?
+6. Does anyone else have a similar experience?
+7. What improvements do you think could be made?
+
+### Conclusion
+* Thank them for their time
+* Let them know their feedback is important to improve the app for all CHWs
+

content/en/design/user-experience-research/user-interviews.md

@@ -8,7 +8,7 @@ aliases:
    - /design/guides/designing-interviews
 ---
 
-User interviews serve the purpose of uncovering opportunities for innovation and for illuminating solutions to problems. 
+User interviews serve the purpose of uncovering opportunities for innovation and for illuminating solutions to problems.
 
 Generative interviews are used in the discovery phase of the development process when you’re looking for opportunities to solve for. Scoped interviews are used when a topic of interest has been identified and you’d like to gain a deeper understanding.
 
@@ -21,13 +21,14 @@ Generative interviews are used in the discovery phase of the development process
     2. Personnel
     3. Location, or connectivity if remote
 
-[Here is a generative interview template](https://docs.google.com/document/d/1Geunh4dANz1Q0nWmAbwVlXbqv8_kcxbee_o1yLi1dQU/edit?tab=t.0).
+[Here is a generative interview template]({{< ref "generative-template" >}})
+
+[Here is a scoped interview template]({{< ref "scoped" >}})
 
-[Here is a scoped interview template](https://docs.google.com/document/d/1q7n9d6xW0G0ypx3jLJf3gz_5NsLY0BX0HLiyBq0IUb0/edit?tab=t.0).
 
 ## Recruiting
 
-For generative interviews, recruit users on a regular cadence for continuous, wide and varied feedback. 
+For generative interviews, recruit users on a regular cadence for continuous, wide and varied feedback.
 
 For scoped interviews, recruit 5-8 users considering the following criteria: