60ed8e2892
* Add commitment config capabilities * Use rpc limit if no end_slot provided * Limit to actually finalized blocks * Support confirmed blocks in getConfirmedBlocks and getConfirmedBlocksWithLimit * Update docs * Add client plumbing * Rename config enum |
||
|---|---|---|
| .. | ||
| .travis | ||
| art | ||
| src | ||
| static | ||
| .eslintrc | ||
| .gitignore | ||
| README.md | ||
| babel.config.js | ||
| build-cli-usage.sh | ||
| build.sh | ||
| convert-ascii-to-svg.sh | ||
| docusaurus.config.js | ||
| offline-cmd-md-links.sh | ||
| package-lock.json | ||
| package.json | ||
| publish-docs.sh | ||
| set-solana-release-tag.sh | ||
| sidebars.js | ||
README.md
Docs Readme
Solana's Docs are built using Docusaurus 2 with npm.
Static content delivery is handled using vercel.
Installing Docusaurus
$ npm install
Local Development
This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server. (You might have to run build.sh first if you run into failures)
$ npm run start
Build Locally
This command generates static content into the build directory and can be
served using any static contents hosting service.
$ docs/build.sh
CI Build Flow
The docs are built and published in Travis CI with the docs/build.sh script.
On each PR, the docs are built, but not published.
In each post-commit build, docs are built and published using vercel to their
respective domain depending on the build branch.
- Master branch docs are published to
edge.docs.solana.com - Beta branch docs are published to
beta.docs.solana.com - Latest release tag docs are published to
docs.solana.com