Skip to content

[Start here] #79

@verytactical

Description

@verytactical
  • should contain minimal description of TON on a single page
  • minimize text, maximize visualization
  • rest of documentation assumes user read this page
  • if there is a difference to how it works on Ethereum/Solana, it should be mentioned in infobox right in the article
  • link reference everywhere

Add 6 points about specifics of TON blockchain from https://blog.ton.org/six-unique-aspects-of-ton-blockchain-that-will-surprise-solidity-developers

"How to read" section:

  • Only start doing this issue when we have Overviews for rest of the sections
  • Describe structure of documentation
  • Link to docs Github repo

Proposed structure

How to read documentation

(structure of documentation, see #261)

Plan

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    scope: top-levelIntroductory pages on top and any highest-level pages later on

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions