Guide re-org milestone issue tracker

[GBKS]

To avoid endless merge conflicts, we should tackle some of the issues in Milestone #15 in a specific order. This issue suggests an order and includes a to-do list we can work through one by one.

Merge conflicts happen when multiple PRs propose changes to the same files (or lines of code). This is likely to happen with this re-org, due the amount of cross-linking in the content.

Content restructuring (do these in order):

• 🎨 [Guide Re-org] - Create a new Resources section #720
• 🎨 [Guide Re-org] - Create How it works section #719
• 🎨 [Guide Re-org] - Update Getting Started #714
• 🎨 [Guide Re-org] - Update Designing bitcoin products #715
• 🎨 [Guide Re-org] - Consolidate Onboarding and Payments into the Daily Spending Wallet reference design #718
• 🎨 [Guide Re-org] - Remove unneeded landing pages #721
• 🎨 [Guide Re-org] - Revise the guide landing page #726
• 🎨 [Guide Re-org] - Update Case studies #716
• 🎨 [Guide Re-org] - Improvements to reference designs  #717
• Reconsider guide section landing pages #723

Other:

• Improve search #713

Ideas (decide whether to do them and how):

• 🎨 [Guide Re-org] - Update site navigation menu #711
• 🎨 [Guide Re-org] - Sidebar updates #712
• Create Case Studies section #722
• Review possible technical implementation of clickable prototypes in the guide #724

Feel free to propose changes to this sequence.

[Bosch-0]

I reckon we could wrap this milestone up when #716 is done. All the remaining issues are more new content additions, not so much content re-orgs.

[GBKS]

I think re-org has just somehow become the shorthand for this effort, but the big idea was to re-think the guide experience which is more broad. So I wouldn't focus too much on that term.

I am OK with this though. #717 and #723 could be split across multiple issues, and #724 could be also be pretty big thing on it's own. We also discovered a bunch of smaller tasks we may want to do first. So if we want to create a new milestone and re-prioritize, happy to do that.

[GBKS]

We discussed this milestone in jam session #24. The remaining tasks have been lingering for a bit, some of them were not actionable and had to be split up, etc. Did some re-organizing and clean-up, we'll close this issue, and tackle the remaining (and new) tasks in upcoming milestones.