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.
We've had several discussions (including yesterdays jam session) around how the current nav structure can be confusing at times:
Automatic cloud backupin bothOnboardingandPrivate key managementsections)Onboardingis about a very specific type of product,Private key managementis about underlying tech, etc. Not always intuitive whyExamples of top-level structures:
User guide,DeploymentandDevelopment, with additionalExplore by topicoptionsmacOS,iOS,watchOSandtvOS, with additionalTechnologiesoptionsTwo starting points:
I want to find info about onboarding UX,I want to understand how multi-key works...)I am wondering if we should bundle
OnboardingandPaymentinto a single megaDaily spendingcase 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.