draft

Publishing Architecture

Deployment and storage model for a Markdown-first MUD site.

Publishing Architecture

The repository is designed around a simple path:

flowchart LR
  A[Markdown vault in content/] --> B[Static site builder]
  B --> C[dist/]
  C --> D[GitHub Pages]
  C --> E[Cloudflare Pages]
  A --> F[Obsidian workspace]
  G[Browser workspace] --> A

Publication targets

GitHub Pages

The GitHub Actions workflow builds the content/ vault into dist/ and publishes it with Pages. This is the simplest public publishing path.

Cloudflare Pages

Cloudflare Pages can run the same build command:

npm run build

and publish the dist directory. The included wrangler.toml documents the expected project settings.

Secure workspace options

Static hosting alone cannot safely write files back to the repository. For human create/update/upload/delete operations, use one of these modes:

• Local-first Git mode — edit Markdown locally in Obsidian or any editor, then commit and push.
• Browser draft mode — use the included site workspace to draft notes in local browser storage, then export Markdown files for commit.
• Encrypted cloud mode — add a Cloudflare Pages Function that encrypts note payloads client-side before storage in Cloudflare R2 or D1. Keep encryption keys outside the server so the storage provider only sees ciphertext.
• Repository PR mode — use GitHub OAuth or a fine-scoped GitHub App to create pull requests instead of directly writing to the default branch.

Recommendation

Start with local-first Git mode plus browser draft mode. Add encrypted cloud mode only when multiple humans need live web editing from untrusted devices.