Files
SpacetimeDB/docs
Zeke Foppa adbfe3b0bd Tidy up CLI reference generation flow (#3226)
# Description of Changes

Some minor cleanups in the flow for regenerating the CLI reference.

# API and ABI breaking changes

None

# Expected complexity level and risk

1

# Testing

- [x] Existing CI passes

Co-authored-by: Zeke Foppa <bfops@users.noreply.github.com>
2025-09-04 20:08:24 +00:00
..
2025-08-22 19:36:47 +00:00
2024-12-31 17:05:13 -05:00
2025-08-15 17:31:30 +00:00

Migration note

We are in the process of moving from the spacetimedb-docs repo to the docs subdirectory of SpacetimeDB. Any new changes should be made there. The spacetimedb-docs repo will only be updated on release. Apologies in advance for any sharp edges while the migration is in progress.

SpacetimeDB Documentation

This repository contains the markdown files which are used to display documentation on our website.

Making Edits

To make changes to our docs, you can open a pull request in this repository. You can typically edit the files directly using the GitHub web interface, but you can also clone our repository and make your edits locally. To do this you can follow these instructions:

  1. Fork our repository
  2. Clone your fork:
git clone ssh://git@github.com/<username>/SpacetimeDB
cd SpacetimeDB/docs
  1. Make your edits to the docs that you want to make + test them locally
  2. Commit your changes:
git add .
git commit -m "A specific description of the changes I made and why"
  1. Push your changes to your fork as a branch
git checkout -b a-branch-name-that-describes-my-change
git push -u origin a-branch-name-that-describes-my-change
  1. Go to our GitHub and open a PR that references your branch in your fork on your GitHub

NOTE! If you make a change to nav.ts you will have to run npm run build to generate a new docs/nav.js file.

CLI Reference Section

  1. Run cargo run --features markdown-docs -p spacetimedb-cli > docs/cli-reference.md
  2. Run pnpm format

We have a CI job which validates internal links. You can run it locally with npm run check-links. This will print any internal links (i.e. links to other docs pages) whose targets do not exist, including fragment links (i.e. #-ey links to anchors).

License

This documentation repository is licensed under Apache 2.0. See LICENSE.txt for more details.