Developer documentation site for the Mezo ecosystem. This repo contains the source for the public docs at https://mezo.org/docs
, built with Astro and Starlight.
- Astro 5 with Starlight for documentation
- Node.js and npm for scripts and tooling
- remark-math and rehype-katex for math/KaTeX support
- sharp for image processing
- starlight-sidebar-topics to manage sidebar topics
We welcome issues and PRs that improve clarity, correctness, and coverage.
- Fork and branch
- Create a descriptive branch from
main
:docs/<topic>-<short-description>
(documentation changes)fix/<scope>-<short-description>
(bugfixes in scripts/config)chore/<short-description>
(non-user-facing maintenance)
- Style and formatting
- Use Prettier via:
npm run lint-fix
- Keep markdown concise, use headings (
##
,###
) and lists, and prefer site-relative links.
- Commit messages
- Follow Conventional Commits when possible:
docs: update mezo-pools user guide
fix(scripts): handle missing asset directory in process step
- Run locally and sanity-check
npm run dev
then review pages you modified athttp://localhost:4321
.- Optional: with the dev server running, check links:
npm run linkcheck-local
- Open a pull request
- Keep PRs focused and small; include context, screenshots if UI/content heavy, and links to related issues.
- The docs site deploy pipeline will build the site; ensure the dev build works before requesting review.
- Reviews & merging
- We require at least one approval from a maintainer.
- Squash-merge preferred; branch names and PR titles should clearly describe the change.
src/content/docs/docs/
— primary markdown content organized by topic (e.g.,users/
,developers/
).public/docs/
— static assets (images, PDFs) served as-is.src/assets/
— project assets referenced by the site.scripts/process-gitbook.js
— parsesSUMMARY.md
, transforms GitBook-style content, and updates sidebar topics inastro.config.mjs
.scripts/linkcheck.js
— simple crawler to check links when the site is running locally.astro.config.mjs
— Astro/Starlight configuration and custom head scripts.
Tips:
- Add or update docs under
src/content/docs/docs/…
. - Place large assets in
public/docs/...
and reference via site-relative paths. - Run
npm run dev
to auto-process and preview changes.
area/users
·area/developers
·content
·typo
·fix
·chore
·good first issue
If you believe you’ve found a security issue that affects Mezo software, please do not open a public issue. Instead, contact us via the channels listed on https://mezo.org
or our GitHub organization profile.
This repository is licensed under GPL-3.0. By contributing, you agree that your contributions will be licensed under the GPL-3.0 license. See LICENSE
for details.
The documentation and scripts in this repository are provided “as is,” without warranties or conditions of any kind. Nothing herein constitutes financial, legal, or investment advice. Use of the software and materials is at your own risk. See the GPL-3.0 license in LICENSE
for the full disclaimer of warranty and limitation of liability.