Hey @Ziithe and @n-orlowski , I have a couple of questions and items to be addressed:

1. Some pages like Interface/UI Kit are quite short. Do you plan on adding more content in future?
2. The images in color.md are not loading correctly - I will work on this and push changes
3. The current external resources page and mockups page is missing. Has it been moved elsewhere?
4. Empathy map, problem statement and mapping hierarchy under this section have they been moved or missing?

I believe @ZiitheH mentioned she synced with you but there are a few things I wanted to clarify:

1. In the updated version we are removing external resources and integrating with specific sections (ex Material Design will be linked to in the UI page)
2. Mockups are to be replaced with the Figma UI kit that Ziithe is working on but if we have the external contributer I'm happy to link to the slides in the UI kit page
3. Empathy map and problem statement are now integrated in the methodologies so we can remove those pages; mapping hierarchy feels like it should be part of configuration but I'm not too sure about this one! What do you think?

Thanks for the clarification @n-orlowski , I think we should keep the Empathy map , Editable Mockups , External Resources and Mapping Hierarchy files and purpose to remove them once they have been incorporated in the said pages.

Gotcha! Resources should already be integrated into the content in this branch and empathy mapping is replaced by our updated methodologies (so we should remove this)

@ZiitheH can you please update to reflect this document's architecture? (changes are adding the Mockup page under UI and Mapping Hierarchy as it's own section)

@mrjones-plip this PR is ready for review. 🎆

@mrjones-plip I added details to the PR about I understood that this PR does. Please let me know if you need more details.

Ah - great! It's a night and day difference after you added an image or two and a couple sentences - it's so much more clear what we're doing. Thanks @andrablaj !

Given these large moves can be tricky and inadvertently cause 404s , I wrote a set of checker scripts in another ticket. While a bit of work, I think we should promote these so anyone can run them and they're easy[ier] to find. I'm happy to do the work myself, but I'd like to block this ticket with that work tracked here.

As well, having this documented and in CI will be a great win for new contributors to the docs, including those outside of medic.

@mrjones-plip I agree with the need for a link checker script to be part of CI. Let's keep this in review until we complete that part. I will let you know if I get to have a look at that script before you do.