cosmos-sdk/docs
Jim Larson d9f3eb027d
feat: structured screens for SIGN_MODE_TEXTUAL (#13434)
## Description

Refs: #11970

Changes target of `SIGN_MODE_TEXTUAL` rendering to be a structured datatype
instead of lines of ASCII text. This avoids the complexities of in-band, signaling and
allows more capable signing devices not to be hindered by the limitations of those less
capable.

---

### Author Checklist

*All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.*

I have...

- [X] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [X] added `!` to the type prefix if API or client breaking change
- [X] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting))
- [X] provided a link to the relevant issue or specification
- [X] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/main/docs/building-modules)
- [X] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#testing)
- [ ] added a changelog entry to `CHANGELOG.md`
- [X] included comments for [documenting Go code](https://blog.golang.org/godoc)
- [X] updated the relevant documentation or specification
- [X] reviewed "Files changed" and left comments if necessary
- [x] confirmed all CI checks have passed
NOTE: changelog intentionally omitted - we'll add an entry when
#11970 is complete.

### Reviewers Checklist

*All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.*

I have...

- [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] confirmed `!` in the type prefix if API or client breaking change
- [ ] confirmed all author checklist items have been addressed 
- [ ] reviewed state machine logic
- [ ] reviewed API design and naming
- [ ] reviewed documentation is accurate
- [ ] reviewed tests and test coverage
- [ ] manually tested (if applicable)
2022-10-15 08:04:36 +00:00
..
architecture feat: structured screens for SIGN_MODE_TEXTUAL (#13434) 2022-10-15 08:04:36 +00:00
docs docs: small ui fixes (#13546) 2022-10-13 19:58:25 +00:00
spec feat: migrate to docusaurus (#13471) 2022-10-10 14:01:53 +00:00
src/css docs: small ui fixes (#13546) 2022-10-13 19:58:25 +00:00
static docs: small ui fixes (#13546) 2022-10-13 19:58:25 +00:00
.gitignore feat: migrate to docusaurus (#13471) 2022-10-10 14:01:53 +00:00
babel.config.js feat: migrate to docusaurus (#13471) 2022-10-10 14:01:53 +00:00
DOC_WRITING_GUIDELINES.md docs: Improve markdownlint configuration (#11104) 2022-02-10 12:07:01 +00:00
docusaurus.config.js remove epoch redirect (#13504) 2022-10-11 13:39:38 +00:00
modules_category.json feat: migrate to docusaurus (#13471) 2022-10-10 14:01:53 +00:00
package-lock.json build(deps): Bump postcss from 8.4.17 to 8.4.18 in /docs (#13541) 2022-10-13 19:17:22 +02:00
package.json build(deps): Bump postcss from 8.4.17 to 8.4.18 in /docs (#13541) 2022-10-13 19:17:22 +02:00
post.sh feat: migrate to docusaurus (#13471) 2022-10-10 14:01:53 +00:00
pre.sh feat: migrate to docusaurus (#13471) 2022-10-10 14:01:53 +00:00
README.md feat: migrate to docusaurus (#13471) 2022-10-10 14:01:53 +00:00
sidebars.js feat: migrate to docusaurus (#13471) 2022-10-10 14:01:53 +00:00
tailwind.config.js docs: small ui fixes (#13546) 2022-10-13 19:58:25 +00:00
vuepress_versions feat: migrate to docusaurus (#13471) 2022-10-10 14:01:53 +00:00

Updating the docs

If you want to open a PR in Cosmos SDK to update the documentation, please follow the guidelines in CONTRIBUTING.md.

Docs Build Workflow

The documentation for Cosmos SDK is hosted at https://docs.cosmos.network and built from the files in the /docs directory. It is built using Docusaurus 2, a modern static website generator.

How It Works

There is a GitHub Action listening for changes in the /docs directory for the main branch and each supported version branch (e.g. release/v0.46.x). Any updates to files in the /docs directory will automatically trigger a website deployment. Under the hood, the private website repository has a make build-docs target consumed by a Github Action within that repository.

README

The README.md is both the README for the repository and the configuration for the layout of the landing page.

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, due to versionning. Note that in case of page reshufling, you must update all links references.

Full

The full GitHub URL to a file or directory. Used occasionally when it makes sense to send users to the GitHub.

Building Locally

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 start

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:3000).

To build documentation as a static website run npm run build.

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.