GitDash is a fork of EmDash that runs entirely on GitHub Pages. There is no server and no database service. Your site's content, schema and settings are JSON files in a public repo, a GitHub Action builds them into a static site, and you edit from the browser with a GitHub token that commits straight to the repo.
Live demo: https://digital-defiance.github.io/GitDash-example/ (source: GitDash-example)
EmDash is built for servers: Cloudflare Workers or Node.js, with SQL at request time. That is the right design for most sites, but it rules out free static hosting, and it means open source projects, docs and personal blogs need infrastructure they would rather not run. GitDash keeps EmDash's content model, templates and admin, and changes where the data lives and when pages are rendered.
The fork stays close to upstream on purpose. Changes are additive (for example, the admin reads its base paths from globalThis.__EMDASH_PATHS__, and defaults are unchanged), so pulling in EmDash releases stays practical.
| EmDash | GitDash | |
|---|---|---|
| Content store | SQLite, D1 or Postgres | JSON files in the repo (one file per row) |
| Rendering | On each request | Static build in a GitHub Action |
| Admin | Served by the site, signs in with passkeys | EmDash's own admin, running in the browser at /studio/; signs in with a fine-grained token or GitHub |
| Saving | Writes to the database | Pending-changes tray, then one atomic commit through the GitHub API |
| Comments | Built in | giscus (commenters need a GitHub account) |
| Plugins | Sandboxed runtime | Browser admin UI and before-hooks, plus build-time after-hooks and cron; public plugin HTTP routes are lost |
Drafts are public because the repo is public, so GitDash suits open source sites.
The demo site and its editor are working end to end. You can create and edit posts and pages, upload media, schedule posts, and change content types and settings, all from the browser. The site gets search, a sitemap, redirects, responsive images, scheduled publishing, webhooks and plugin cron jobs in the build. You can import a Jekyll site or a Markdown folder, add a contact form, and offer "Sign in with GitHub". Not available: users and passkeys, and anything that needs a server at request time (public plugin routes, anonymous comments without a GitHub account).
Experimental: it works and is tested, but expect rough edges, and the patched admin and core come from release files on this repository rather than from EmDash itself. Design, decisions and the checklist are in gitpages-port/: start with SPEC.md and TODO.md. Steps only the site owner can do are in OWNER-STEPS.md.
- Use GitDash-example as a template (Use this template, public repository) or fork it.
- Turn on Pages: Settings, Pages, Source: GitHub Actions. The workflow builds and deploys, and the site appears at
https://<owner>.github.io/<repo>/. - Open
/studio/on your site and sign in with a fine-grained token (Contents: read and write, that repo only). Edit, then Commit.
SETUP.md has the full walkthrough and the optional extras: comments, scheduled posts, webhooks, plugin cron, importing a Jekyll site, a contact form, and GitHub sign-in. The build scripts and studio are the npm package @digitaldefiance/gitdash-pages (README).
The rest of this README is EmDash's own, kept as is.
A full-stack TypeScript CMS built on Astro. EmDash takes the ideas that made WordPress dominant -- extensibility, admin UX, a plugin ecosystem -- and rebuilds them on serverless, type-safe foundations. Plugins run in sandboxed Worker isolates, solving the fundamental security problem with WordPress's plugin architecture.
npm create emdash@latestOr deploy directly to your Cloudflare account:
EmDash runs on Cloudflare (D1 + R2 + Workers) or any Node.js server with SQLite. No PHP, no separate hosting tier -- just deploy your Astro site.
EmDash ships with three starter templates:
|
A classic blog with sidebar widgets, search, and RSS.
|
A photo-led landing page built from modular blocks.
|
A visual portfolio for showcasing creative work.
|
WordPress was built for a different era. Running WordPress today means managing PHP alongside JavaScript, layering caches to get acceptable performance, and knowing that 96% of WordPress security vulnerabilities come from plugins. EmDash is what WordPress would look like if you started from scratch with today's tools.
Sandboxed plugins. WordPress plugins have full access to the database, filesystem, and user data. A single vulnerable plugin can compromise the entire site. EmDash plugins run in isolated Worker sandboxes via Dynamic Worker Loaders, each with a declared capability manifest. A plugin that requests content:read and email:send can do exactly that and nothing else.
export default () =>
definePlugin({
id: "notify-on-publish",
capabilities: ["content:read", "email:send"],
hooks: {
"content:afterSave": async (event, ctx) => {
if (event.content.status !== "published") return;
await ctx.email.send({
to: "editors@example.com",
subject: `New post: ${event.content.title}`,
});
},
},
});Structured content, not serialized HTML. WordPress stores rich text as HTML with metadata embedded in comments -- tying your content to its DOM representation. EmDash uses Portable Text, a structured JSON format that decouples content from presentation. Your content can render as a web page, a mobile app, an email, or an API response without parsing HTML.
Built for agents. EmDash publishes agent skills that teach coding assistants its APIs, a CLI that lets agents manage content and schema programmatically, and a built-in MCP server so AI tools like Claude and ChatGPT can interact with your site directly.
Runs anywhere. EmDash uses portable abstractions at every layer -- Kysely for SQL, S3 API for storage -- that work with SQLite, D1, Turso, PostgreSQL, R2, AWS S3, or local files. It runs best on Cloudflare, but it's not locked to it.
EmDash is an Astro integration. Add it to your config and you get a complete CMS: admin panel, REST API, authentication, media library, and plugin system.
// astro.config.mjs
import emdash from "emdash/astro";
import { d1 } from "emdash/db";
export default defineConfig({
integrations: [emdash({ database: d1() })],
});Content types are defined in the database, not in code. Non-developers create and modify collections through the admin UI. Each collection gets a real SQL table with typed columns. Developers generate TypeScript types from the live schema:
npx emdash typesQuery content using Astro's Live Collections -- no rebuilds, no separate API:
---
import { getEmDashCollection } from "emdash";
const { entries: posts } = await getEmDashCollection("posts");
---
{posts.map((post) => <article>{post.data.title}</article>)}Content -- Blog posts, pages, custom content types. Rich text editing via TipTap with Portable Text storage. Revisions, drafts, scheduled publishing, full-text search (FTS5), inline visual editing.
Admin -- Full admin panel with visual schema builder, media library (drag-drop uploads via signed URLs), navigation menus, taxonomies, widgets, and a WordPress import wizard.
Auth -- Passkey-first (WebAuthn) with OAuth and magic link fallbacks. Role-based access control: Administrator, Editor, Author, Contributor.
Plugins -- definePlugin() API with lifecycle hooks, KV storage, settings, admin pages, dashboard widgets, custom block types, and API routes. Sandboxed execution on Cloudflare via Dynamic Worker Loaders, and on Node.js in a workerd child process.
Agents -- Agent skills for AI-assisted site, plugin, and theme development. CLI for programmatic site management. Built-in MCP server for direct AI tool integration.
WordPress migration -- Import posts, pages, media, and taxonomies from WXR exports, the WordPress REST API, or WordPress.com. Agent skills help port plugins and themes.
| Layer | Cloudflare | Also works with |
|---|---|---|
| Database | D1 | SQLite, Turso/libSQL, PostgreSQL |
| Storage | R2 | AWS S3, any S3-compatible service, local filesystem |
| Sessions | KV | Redis, file-based |
| Plugins | Worker isolates (sandboxed) | workerd child process (sandboxed) |
EmDash is stable and ready for production. The core packages (emdash, create-emdash, and the @emdash-cms admin, auth, blocks, and Cloudflare packages) follow semantic versioning: breaking changes ship only in major releases and are called out in the changelog. First-party plugins and plugin tooling are still on 0.x and may change between minor releases.
We welcome contributions, feedback, plugins, themes, and ideas.
npm create emdash@latestSee the documentation for guides, API reference, and plugin development.
This is a pnpm monorepo. To contribute:
git clone https://github.com/emdash-cms/emdash.git && cd emdash
pnpm install
pnpm buildRun the primary development demo (demos/simple/; Node.js + SQLite, no Cloudflare account needed):
pnpm --filter emdash-demo devOpen the admin at http://localhost:4321/_emdash/admin.
pnpm test # run all tests
pnpm typecheck # type check
pnpm lint:quick # fast lint (< 1s)
pnpm format # format with oxfmtSee CONTRIBUTING.md for the full contributor guide.
packages/
core/ Astro integration, APIs, admin UI, CLI
auth/ Authentication library
blocks/ Portable Text block definitions
cloudflare/ Cloudflare adapter (D1, R2, Worker Loader)
plugins/ First-party plugins (forms, embeds, SEO, audit-log, etc.)
create-emdash/ npm create emdash scaffolding
gutenberg-to-portable-text/ WordPress block converter
templates/ Starter templates (blog, marketing, portfolio, starter, blank)
demos/ Development and example sites
docs/ Documentation site (Starlight)


