If you want to open a PR on the Cosmos SDK to update the documentation, please follow the guidelines in the CONTRIBUTING.md
- Docs translations live in a
docs/country-code/
folder, wherecountry-code
stands for the country code of the language used (cn
for Chinese,kr
for Korea,fr
for France, ...). - Always translate content living on
master
. - Only content under
/docs/intro/
,/docs/basics/
,/docs/core/
,/docs/building-modules/
anddocs/interfaces
needs to be translated, as well asdocs/README.md
. It is also nice (but not mandatory) to translate/docs/spec/
. - Specify the release/tag of the translation in the README of your translation folder. Update the release/tag each time you update the translation.
The documentation for the Cosmos SDK is hosted at https://cosmos.network/docs/
built from the files in this (/docs
) directory for
master.
There is a CircleCI job listening for changes in the /docs
directory, on
the master
branch. Any updates to files in this directory
on that branch will automatically trigger a website deployment. Under the hood,
the private website repository has a make build-docs
target consumed by a CircleCI job in that repo.
The README.md is also the landing page for the documentation on the website. During the Jenkins build, the current commit is added to the bottom of the README.
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.
Make sure you are in the docs
directory and run the following commands:
rm -rf node_modules
This command will remove old version of the visual theme and required packages. This step is optional.
npm install
Install the theme and all dependencies.
npm run serve
Run pre
and post
hooks and start a hot-reloading web-server. See output of this command for the URL (it is often https://localhost:8080).
To build documentation as a static website run npm run build
. You will find the website in .vuepress/dist
directory.
First, run make tools
from the root of repo, to install the swagger-ui tool.
Then, edit the swagger.yaml
manually; it is found here
Finally, run make update_gaia_lite_docs
from the root of the repo.
We are using Algolia to power full-text search. This uses a public API search-only key in the config.js
as well as a cosmos_network.json configuration file that we can update with PRs.
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 Tendermint Core repo.
- Execute the following command at the root directory to install the swagger-ui generate tool.
make tools
- Edit API docs
- Directly Edit API docs manually:
client/lcd/swagger-ui/swagger.yaml
. - Edit API docs within the Swagger Editor. Please refer to this document for the correct structure in
.yaml
.
- Directly Edit API docs manually:
- Download
swagger.yaml
and replace the oldswagger.yaml
under foldclient/lcd/swagger-ui
. - Compile gaiacli
make install