Open source · MIT · built on EmDash
A CMS that lives in your Git repository.
GitDash runs the EmDash CMS with no server and no database. Your content is JSON in a repo, CI builds a static site, and you edit in the browser with an admin that commits straight back to Git.
/studio/content/ec_posts/01M7….jsonstatic HTML, search, sitemap, RSSFeatures
Everything EmDash does for editors, nothing to run
Content is just files
Posts, pages, menus, settings and the schema are JSON in content/, one file per row. Diff them, review them in a pull request, and roll back with git.
EmDash's own admin, in the browser
Open /studio/ and you get the real EmDash editor, running on SQLite compiled to WebAssembly. No server behind it.
One commit per save
Edits collect in a pending-changes tray that survives a reload. Commit writes them all as one atomic commit, and merges if someone pushed meanwhile.
Free static hosting
A CI job turns the JSON into a fast static site. No database bill, nothing to patch, nothing to keep running.
Media, search and SEO built in
Image uploads with responsive sizes, Pagefind search, a sitemap, robots.txt, redirects and an RSS feed.
Scheduled posts, hooks and cron
Schedule a post and an hourly job publishes it. Plugin after-hooks, webhooks and cron jobs run in CI.
Comments and contact forms
giscus or GitLab comments on posts, and a contact form that posts to a form service, your own Worker, or issues.
Bring your old site
Import a Jekyll site or a folder of Markdown, front matter and images included.
Hosting
Host it where you already are
The build is the same everywhere. Pick a host, and the base path and site address are worked out for you.
GitHub Pages
The original target. The included workflow builds on every push and deploys with Actions.
GitLab Pages
The same build in GitLab CI. The studio commits through the GitLab API, with GitLab sign-in and comments.
Netlify
Connect the repository and Netlify builds it with the included netlify.toml.
Cloudflare Pages
Point Cloudflare Pages at the repository and it serves the same static build at the edge.
Get started
Your own site in three steps
Copy the template
Open GitDash-example and choose Use this template, or fork it.
Turn on Pages
In the new repository: Settings, Pages, Source: GitHub Actions. The first build publishes your site.
Edit in the studio
Open
/studio/on your site and sign in with a fine-grained token (Contents: read and write, that repository only). Edit, then Commit.
Or build it locally
npm install
npm run build # content/*.json → SQLite → dist/client
npm run previewRead the full setup guide·@digitaldefiance/gitdash-pages on npm
Live demo
This site is a GitDash site
These posts are sample content. Open the studio, change one, and see the commit it makes.
Built in the open by Digital Defiance
GitDash is made by an open source engineering guild. Issues, ideas and pull requests are welcome.