Skip to content

[Start here] Describe structure of documentation #261

@verytactical

Description

@verytactical

Do not take this ticket until we're done with figuring out top-level structure of the documentation. Can be done at the end of hackathon.

  • Describe structure of documentation
    • Basics: must read
    • Step by step: guides for specific common cases
    • Tooling: stuff developer needs
    • Standard contracts: vetted good contracts that already exist
    • Foundations: how TON works
    • Techniques: how to develop new good contracts
  • Link to its Github repo

Metadata

Metadata

Assignees

Labels

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

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions