Source files for the Jamdesk documentation site. This repo contains the MDX content, not the Jamdesk platform source code. It also serves as a working example of a Jamdesk project — the same docs.json + .mdx files structure that any Jamdesk user would create.
Jamdesk is a documentation platform that builds docs sites from MDX files in a GitHub repo. Push and your site deploys to a global CDN. It supports OpenAPI specs, AI chat (RAG + Claude), MCP server integration, automatic llms.txt generation, built-in analytics, and custom domains.
jamdesk-docs/
├── docs.json # Site config (navigation, theme, colors, redirects)
├── introduction.mdx # Homepage
├── quickstart.mdx # Getting started guide
├── ai/ # AI features (chat, MCP, llms.txt, Claude Code, Cursor)
├── api-reference/ # OpenAPI example pages
├── builds/ # Build system docs
├── cli/ # CLI documentation
├── components/ # 22 MDX component reference pages
├── content/ # Writing guides (MDX, code blocks, frontmatter, SEO)
├── customization/ # Theming, branding, custom CSS/JS
├── deploy/ # Deployment (custom domains, Vercel, Cloudflare, AWS)
├── development/ # Local preview, VS Code extension
├── help/ # Help Center (account, billing, troubleshooting)
├── integrations/ # GitHub, Google Analytics, Plausible, Slack
├── images/ # Logos and screenshots
├── openapi/ # OpenAPI spec files
└── setup/ # Project configuration and analytics
This repo is content only. To preview locally, install the Jamdesk CLI:
npm install -g jamdesk
jamdesk devThe dev server starts at http://localhost:3000 with hot reload.
Contributions are welcome — typo fixes, clarifications, new examples, or missing docs.
Quick edits: Click the pencil icon on any file in GitHub to edit directly. Changes auto-deploy when merged.
Larger changes:
- Fork this repo
- Create a branch (
git checkout -b fix/typo-in-quickstart) - Edit the
.mdxfiles (every page needstitleanddescriptionfrontmatter) - Preview locally with
jamdesk dev(optional) - Submit a pull request
Found an issue? Open an issue to report inaccuracies, request new content, or suggest improvements.
- Start with why, then show how — include working examples
- Use MDX components:
<Steps>,<Tabs>,<Card>,<Callout>,<Accordion>,<Code> - Link related pages at the bottom with "What's Next?" cards
- Page paths in
docs.jsonnavigation omit the.mdxextension
- Create an
.mdxfile in the appropriate directory - Add
titleanddescriptionfrontmatter - Add the page path to
docs.jsonunder the correct navigation group
All site configuration lives in docs.json — navigation structure, theme, colors, API settings, redirects, and integrations. The schema is published at jamdesk.com/docs.json and can be referenced with "$schema": "https://www.jamdesk.com/docs.json" for editor autocompletion. See the docs.json reference for full documentation.
This project is licensed under the Apache License 2.0.