-
Notifications
You must be signed in to change notification settings - Fork 25
Open
Labels
backlogTo organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.To organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.
Description
Problem / Why
“Start here” currently mixes onboarding with deep protocol details and doesn’t provide a clean first-time-reader path. New devs struggle to understand what to read first, what’s optional, and how to get to building quickly.
What to do
Redesign the “Start here” page into a small number of clearly-labeled sections, each with a 1–2 sentence explanation aimed at a first-time reader, and a “what to do next” link.
Proposed sections (draft)
- What is TON
Short mental model: TON as a scalable, message-driven blockchain for apps. - What you can build
Smart contracts, tokens, mini apps, payments; set expectations. - Core concepts you must know (only the basics)
Accounts/contracts, messages, fees; include high-level defs (workchain, node). No deep dives. - Recommended stack (Best practices)Tolk + Blueprint (explicit), plus minimal prerequisites.
- Your first steps (Hands-on path)
Install, create project, run tests, deploy to testnet, interact from a script. - How to interact with the network (practical)
Wallets, TON Connect, APIs, explorers — high level only, link out. - Next learning paths
“Smart contracts deeper”, “Tokens”, “TON Connect”, “Run a node” (optional), “Advanced internals” (optional).
Metadata
Metadata
Assignees
Labels
backlogTo organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.To organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.