[Smart contracts > Fundamentals] Add an illustration of a smart contract’s layout (code + data + balance + address) #1692
Description
Problem / Why
New developers don’t have a clear mental model of what a TON smart contract “is” structurally. Without a visual, concepts like code vs data (state), balance, address, and messages in/out remain abstract.
What to do
Add a simple illustration that shows a TON smart contract account layout, including:
- Address
- Balance (TON / tokens as applicable)
- Code (TVM bytecode)
- Data / State (persistent storage)
- Interfaces / entrypoints (external/internal message handlers, optional)
- Messages: incoming (external/internal) and outgoing (internal) arrows
Mermaid diagrams could be a great start.
Optional callouts:
- “Get methods are off-chain reads”
- “State changes happen during transaction execution”
Acceptance criteria
- One clear diagram is included in the relevant fundamentals page.
- Diagram matches TON terminology used in docs.
- The surrounding text references the diagram and explains it in 3–6 sentences.