Different tasks completed during self-learn time during onboarding.
Horizontal nav thoughts:
- The driver was to allow a user to pinpoint where they were within their journey using a horizontal nav design design.
- Data was used to firstly set a target of reducing the volume of Google exits by 30%. However, based on the volumetric data of docs being across 30 products and 800 articles, it was idemtified that the content was too expansive to fit into this design.
- Principles: Design and strategy (user-centred and shipping to learn), content models.
Product idea #1565 REST API Content Structure
- What is the desired outcome? Up;date REST API calendar structure to match current content file versions used already.
- What is the issue's priority level? High
- What sub-teams will be included in the work for this issue?
- What are the scale, significance, and urgency for this issue? All users using the REST API Docs are impacted; the results of this project would be used frequently and its impact would be long-lasting; while not urgent now, at some point it'll become very urgent.
Releases ad content overview:
- Tier 1 release = Copilot for individuals
- Tier 2 release = Advisory database supports Malware advisories
- Tier 3 release = Enabling presence in GHES
- Tier 4 release = View screen and notebooks in GHES
- Might need docs = Docs TBD
It's esstential to have principles in content design as that underpins your whole content design solution and strategy at every level. Design and strategy is the thought process about how content serves the user and their needs; without this, there is nothing to hang the content off, or any inituitive, or thought out, workstream. The style guides and content models ensure a consistent experience for the user, with each writer providing a consistent approach towards their output.
This is evident within docs by the groupings of similar-themes of content together, and the lack of duplication.