docs: getting-started what-next page

[marc0olo]

Summary

• Routing page with 7 developer paths: backend, full-stack, chain fusion, DeFi, governance, AI, concepts
• Each path has a "start with" link and "then explore" progression
• Synthesizes developer journey analysis — no upstream equivalent

Sync recommendation

hand-written — original content synthesizing the developer journey

[marc0olo]

Review: What Next?

Suggestions

• Frontmatter icskills field removed: The stub had icskills: []. While this page has no specific skill association, every other getting-started page retains the field. For consistency, consider keeping icskills: [] so the frontmatter schema is uniform across the section.
• Dogecoin description could be more precise: "work with Dogecoin using the same ECDSA patterns as Bitcoin" — consider "the same chain-key ECDSA signing" to be more consistent with the chain fusion terminology used elsewhere on the page.
• "Understand the platform first" placement: This section is at the bottom, but developers who prefer concepts-first would benefit from seeing it earlier. Consider adding a brief callout in the intro like "Prefer to understand the platform before building? Jump to Concepts." This keeps action-oriented paths front and center while giving concepts-first readers a quick escape hatch.

Verified

• All 27 internal links resolve to existing files
• Single external URL (https://skills.internetcomputer.org) matches linking rules
• No dfx references, no .mdx/JSX, no banned URLs
• All links use relative paths with .md extension
• Frontmatter is complete: title, description, sidebar.order present and consistent with body
• Content brief fully addressed: stub asked for 4-5 paths with 2-3 sentences each; PR delivers all 5 required paths (backend, full-stack, chain fusion, DeFi, governance) plus 2 bonus sections (AI-assisted development, concepts)
• Source material consulted: developer journey analysis aligns with path ordering
• Upstream comment (<!-- Upstream: hand-written -->) present and appropriate
• Plain markdown, no JSX, all code examples under 30 lines

[marc0olo]

Feedback addressed:

• Changed Dogecoin description to use "chain-key ECDSA signing" for consistency with chain fusion terminology
• Added concepts callout in the intro paragraph linking to "Understand the platform first" section
• Added icskills: [] to frontmatter for consistency with other getting-started pages

[marc0olo]

Follow-up review: What Next?

Must fix

• Opening paragraph assumes reader state: "You have a running canister and understand how an ICP project is structured" — a developer may arrive from search, a blog post link, or by browsing the sidebar without having done the quickstart. Replace with something that orients without assuming, e.g.: "Choose your next step based on what you want to build. Each path links to the first guide you should read, with a suggested progression from there."

Suggestions

• Surface the default path: "This is where most developers start after the quickstart" is buried in the Backend development body text. This is the most useful piece of information on the page — make it more prominent, either in the intro ("Not sure where to start? Most developers begin with backend development.") or via visual emphasis.
• Move "Understand the platform first" up: Currently last, which signals it's optional. For newcomers without a clear goal, it's often the right starting point. Consider moving it to second position (right after the intro) or adding a callout in the intro for developers who want to understand before building.

[marc0olo]

Feedback addressed:

• Rewrote opening paragraph to not assume reader completed the quickstart — now standalone
• Surfaced default path ("Most developers begin with backend development") in the intro
• Moved "Understand the platform first" section from bottom to second position

[Copilot]

Pull request overview

This pull request implements the content for the "What Next?" guide page, which serves as the critical routing page for developers after completing the quickstart. The page provides 6 main development paths (plus a concepts-first alternative and AI development) with clear guidance on which path to follow based on the developer's goals. Each path links to the first recommended guide and suggests progression through related topics.

Changes:

• Replaced TODO comment and content brief with actual guide content
• Added 7 main sections: Understand the platform first, Backend development, Full-stack applications, Chain fusion (cross-chain), DeFi and tokens, Decentralized governance, and AI-assisted development
• Each section includes consistent formatting with "You want to", description, "Start with", and "Then explore" subsections
• Added links to 25+ related concept and guide pages across all sections

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.