Review the information architecture of the site

[MatMoore]

Problem

When we moved to the tech docs template, we directly translated all the markdown files we had into pages in the tech docs.

Because we've kept the existing structure, parts of the site are disconnected from others. For example, if you're on a competency page there is no way to navigate back up to the career path, and to other competencies, other than inline links and the back button.

But we can do stuff in the tech docs that we couldn't do with plain markdown, and we can do more to show users where they are in the structure of the site. See https://github.com/alphagov/gds-tech-learning-pathway/issues/92 for more info.

Task

I think we should review the overall information architecture and make some recommendations for future changes (I'm happy to help out with this).

[MatMoore]

Some things to think about:

• Currently the main organising structures are competencies and resource lists. What information are we providing that doesn't fit this pattern?
• Are we doing enough to surface this structure to users? Is it clear what you're viewing if you followed a link to some specific page?
• Is it easy to move between related things?
• Is it easy to go back to high level pages after viewing resource lists/competencies?
• What are the most important user journeys? Are there any "funnels" we should pay attention to?

[MatMoore]

I'm going to mark this as done for now. We haven't answered all these questions but https://github.com/alphagov/gds-tech-learning-pathway/pull/108 should address the main problems.