The thinking about how we structure linking throughout the docs.
This is a range of people, but it covers someone who has just started programming to an experienced programmer who is interested in understanding a new language. For them, the TypeScript website is exploratory.
On a desktop, you're doing deeper learning usually, with a specific goal in mind.
Four main user goals:
- Understand what TypeScript is
- Try TypeScript
- Install TypeScript
- Learn the language
- Homepage
- Homepage Footer -> Why TypeScript
- Homepage -> Handbook
- Homepage Header -> Download
- Homepage -> Install Locally -> Download
- Homepage -> Try it out -> Examples -> Install -> Playground
- Homepage -> Install Locally -> Tutorials -> Install -> Playground
- Homepage -> Learn
- Homepage -> Learn
On mobile the first user experience is oriented towards shallow learning ('what is this typescript thing?' and learning enough to know that you'd want to come back with an IDE)
Two main user goals:
- Understand what TypeScript is
- Learn a bit of the language
- Homepage
- Homepage -> Why TypeScript
- Homepage -> Download -> Learn
- Homepage -> Learn
This is a narrower range of people, representing someone with a bit of confidence in their TypeScript knowledge and are coming back to the website as a reference tool.
Three main user goals:
- Improve my knowledge on TypeScript
- Get to a specific bit of information I'm looking for
- Work on and share code
User routes:
- Homepage -> Download -> Learn
- Homepage -> Learn
Entry points:
- Search via search engines (handled by SEO, titles, headers, head metadata, HTML5 attributes, JSON schemas)
- Search via in-site search
- Navigation route from home to specific handbook
User routes:
- Homepage "try button"
- Homepage -> Playground
- Homepage -> Tools -> Playground
- Homepage Footer -> Code Samples -> Playground
Two main user goals:
- Improve my knowledge on TypeScript
- Get to a specific bit of information I'm looking for
Homepage -> Learn