tact-docs

tact-docs copied to clipboard

They have to be short, straight-to-the-point and re-usable, so simply copy-pasting solutions to problems here is discouraged. https://github.com/ton-community/tact-challenge

novusnota

This might require reformatting the existing files

anton-trunov

1. All the links in docs should be automatically checked each week for the valid response of the servers (200 or 301/302). 2. Optional: Add a pre-commit or pre-push hook...

novusnota

The spellchecker should support adding custom words. It should be documented how to add new words to the dictionary

anton-trunov

Cover a system of sufficiently large interacting realistic contracts

2

This should include interaction with the standard contracts in the TON ecosystem.

anton-trunov

Proposal: An easy way to create new pages and sections

2

Currently, one needs to know what and where to place in the docs. It would be nice to have a simple cli or small scripts controlled from `scripts` section in...

novusnota

Fix typos: "it's" vs "its"

2

There is a bunch of typos like this. For instance, "it manipulates it's own state" -> "it manipulates its own state".

anton-trunov

Docs lack contributing info

2

It's necessary to have: * Overview of the project structure * Help on adding new pages and sections * Guidance on adding translations (once #80 and #86 get resolved) It...

novusnota

Add a ready-built GitHub Codespaces instance for quick and convenient contributions

2

This should include VS Code plugins for Tact, FunC & installed dependencies for contributing to docs. More on Codespaces: https://github.com/features/codespaces. Depends on #89 and #88.

novusnota

See: https://github.com/ton-community/tutorials Maybe, the current getting-started guide would be superseded by this series of 4 tutorials.

novusnota