Design system
Tokens and components you own
Components are copied into your site, shadcn style. Edit them freely. One tokens file drives every color, radius and font.
A dark design system, a content pipeline that reads your repository, and a scaffold that publishes to GitHub Pages. MIT licensed.
npx docs-sitekit init01 · Why
Design system
Components are copied into your site, shadcn style. Edit them freely. One tokens file drives every color, radius and font.
Your repository is the source
Markdown in docs, examples and the changelog becomes pages. Relative links keep working on GitHub and on the site.
Safe to publish
Unknown config keys fail the build. A scan looks for credentials and internal hosts before anything is deployed.
Fast by default
Every route is a real HTML file with its own title. Only the copy buttons and the mobile menu ship JavaScript.
02 · Docs
Guides and reference for using sitekit.
Create a documentation site for a repository in a few minutes.
The design system is a set of React components, written in the shadcn style and rendered at build time. Only the copy button and the mobile menu hydrate.
design/tokens.json is the single source of truth for colors, radius, fonts, layout and motion. npm run build:tokens turns it into CSS variables.
How a markdown file becomes a page.
The site is static, so GitHub Pages serves it directly.
03 · Examples
Working examples you can copy and adapt.