[Top-level articles] Redesign onboarding flow (Spike → Task with subtasks) #1985
Description
Issues with the current one:
- Beginners are led to smart contracts, while most of them want/need to make dApps.
- Creation of new dApps should be highlighted before extension/integration of existing ones with TON. Yet, integrations must remain visible, since some of the audience want to add TON quickly and offboard from the docs.
- Journeys on the landing page are nice-ish, but do not meet all the needs for a) quick navigation, b) smooth onboarding of different personas.
- Landing page should take some burden off of the start-here page and showcase documentation sections with quick links to the most popular ones (see, e.g., Cloudflare doc-in-docs approach).
Additional limitations:
- Keep the flows of existing users largely untouched: that is, do no harm to people who are already familiar with the documentation and/or TON itself, and don't move stuff around recklessly. In practice, this means that everything from the Ecosystem section down should stay the same — the redesign targets the landing page and a few top-level pages we have.
- This is a blocker for making bigger changes to the Contract development section, since it is a big part of the current onboarding flow (that we want to change).
Propose ideas here or during syncs