PROPOSAL: Extend Unity tutorial with "How do I...?" Code gallery

[bfops]

This adds a markdown version of a proposal that has been Living in Notion so far.

[bfops]

View in Markdown

[bfops]

Adding just @jdetter for initial review, since you're the most functionally familiar with the Unity tutorial.

[gefjon]

I would consider the universally-popular "Frequently Asked Questions."

If these will specifically be for features added to the Unity tutorial game, I would consider the more-specific "Add-on Features."

[bfops]

Notes from tb with John:

• zeke's goal (for first pass): Get as many wins as possible without making any real decisions
• Think about: Where do we want our docs+onboarding to be on MainNet launch?
  • Looking real
  • Functioning tutorial
  • Polished onboarding funnel
  • Clear use cases we meet
  • "Coming soon" / future features, etc.
  • Ways to engage
• tutorial/docs analytics
  • what's the current state of our GA?
  • can we see users flowing through our current tutorial/docs?
  • where are people falling off?
• videos are probably more consumable for many users than reading docs
  • as well as specific "finished projects" such as games rather than pieces
  • (the more we can make these out of composable parts in our "code demo" section/videos, the easier to do+maintain those)
• we should provide github repo, folders, etc. for tutorial parts
  • (maybe fresh start on github repo?)
  • finished download urls
• we can start now:
  • (tech note: surface subsections in the sidebar)
  • low-hanging stuff (bugs, stale names, upgrading spacetime version)
  • breaking up the tutorial into pieces
  • per-section links into github parts
  • greyboxing the assets, more generic where possible (and fewer assets)
  • start with pt1, pt2+pt3 might be abandoned to the wolves for now

[dylanh724]

Possibly related: Dylan/unity-tutorials-csharp-parity #31