The documentation for Tendermint Core is hosted at:
built from the files in this (/docs) directory for
master
and develop,
respectively.
There is a Jenkins job listening for changes in the /docs directory, on both
the master and develop branches. Any updates to files in this directory
on those branches will automatically trigger a website deployment. Under the hood,
a private website repository has make targets consumed by a standard Jenkins task.
The README.md is also the landing page for the documentation on the website.
The config.js generates the sidebar and Table of Contents on the website docs. Note the use of relative links and the omission of file extensions. Additional features are available to improve the look of the sidebar.
NOTE: Strongly consider the existing links - both within this directory and to the website docs - when moving or deleting files.
Relative links should be used nearly everywhere, having discovered and weighed the following:
Where is the other file, relative to the current one?
- works both on GitHub and for the VuePress build
- confusing / annoying to have things like:
../../../../myfile.md - requires more updates when files are re-shuffled
Where is the other file, given the root of the repo?
- works on GitHub, doesn't work for the VuePress build
- this is much nicer:
/docs/hereitis/myfile.md - if you move that file around, the links inside it are preserved (but not to it, of course)
The full GitHub URL to a file or directory. Used occasionally when it makes sense to send users to the GitHub.
Not currently possible but coming soon! Doing so requires
assets held in the (private) website repo, installing
VuePress, and modifying the config.js.
Because the build processes are identical (as is the information contained herein), this file should be kept in sync as much as possible with its counterpart in the Cosmos SDK repo.