Re-consider the navigation and browsing experience

[GBKS]

We've had several discussions (including yesterdays jam session) around how the current nav structure can be confusing at times:

• Pages with the same names (for example, Automatic cloud backup in both Onboarding and Private key management sections)
• Onboarding is about a very specific type of product, Private key management is about underlying tech, etc. Not always intuitive why

Examples of top-level structures:

• BTCPay docs: main sections are User guide, Deployment and Development, with additional Explore by topic options
• Apple Human Interface Guidelines: main sections are macOS, iOS, watchOS and tvOS, with additional Technologies options

Two starting points:

• What content do we have, is there a better natural structure?
• What entry points do readers want (I want to find info about onboarding UX, I want to understand how multi-key works...)

I am wondering if we should bundle Onboarding and Payment into a single mega Daily spending case study. It is pretty much a more elaborate version of the other case studies we have. I think the best way to resolve this task is by mocking things up in Figma.

[Bosch-0]

I've wanted to bundle Onboarding + Payments for awhile and think this makes a lot of sense compared to the current structure - big ACK from me.

I like the idea of having a more intuitive landing page for the guide, kind of how BTCPay docs and Apple human guidelines initial view is. Some example sections we could have displayed in a similar manner to the Apple human interface guidelines:

• Getting started (Jumps straight to start of the guide. This would be targeted at designers new to Bitcoin and want to read the Guide from start to finish rather than jump into the meat and potatoes / practical sections of the Guide).
• Daily spending (focuses on Lightning first, mobile, non-custodial wallet application design)
• Savings (Focuses on multi-key, cold storage application design)
• Resources? (For all the supplementary / underlying tech chapters)

If we go with this structure and have the main sections of the guide essentially case studies, do we really need the Case studies chapter?

We should also have a search as well as some suggested topics on this landing page for easier navigation.

Another suggestion is having section headings in the sidebar nav like BTCPay has below:

I will do up some mockups for my above suggestions to explain this more clearly.

[Bosch-0]

Relevant Figma brainstorming file for this issue: https://www.figma.com/file/5amvNM95DkHFpOnVzzoAyK/Guide-visual-review-210504?node-id=201%3A2

[GBKS]

We had a brainstorm session for this issue yesterday. Here are the relevant links:

• Recording of the 2-hour session
• FigJam used in the session
• Text summary of the proposed changes
• Video summary (10 minutes) of the proposed changes (watch this)

And here's a visual summary, comparing the current and proposed landing pages (this is discussed in the summary video above).

Next step is to run this past the community and get more feedback. We also want to have a call to invite people to share their ideas. Then we'll revise the plan again and try to implement this in logical steps (inviting feedback again with each step).

[GBKS]

See milestone #15 for issues that came out of these discussions.

[GBKS]

Wrapping up milestone #15 now. A few remaining issues were not completed, but instead split into new issues, or will be tackled separately in other milestones.