CMS

Structured content
that stays Markdown.

Define schemas, edit frontmatter without YAML typos, and browse every entry in a table — while the content stays plain files in a repo.

studioarticles/the-quiet-web.md
Published 2m ago
MarkdownUTF-8
---
title: The Quiet Web
slug: the-quiet-web
status: published
published: 2026-11-04
tags: [essays, design]
---

# The Quiet Web
Small sites, slow pages, and the return of **writing for people**.

A decade of feeds taught us to perform. The quiet web asks for something else.
![Cover](/media/quiet-web.jpg)
Entrylive
Frontmatterschema: Article
titleThe Quiet Web
slugthe-quiet-web
statuspublished
published2026-11-04
tagsessaysdesign

The Quiet Web

Small sites, slow pages, and the return of writing for people.

A decade of feeds taught us to perform. The quiet web asks for something else.

quiet-web.jpg · 148 KB
AutosavedMarkdown · plain text · forever

CMS

A content model your developers can read

The schema lives in a file. The entries live in files. Your deploy pipeline already understands both.

Schemas per folder

Give a folder a schema with string, number, date, boolean and array fields, and every entry is validated against it.

Frontmatter without typos

Edit metadata through a guided key-value panel with validation, instead of hand-writing YAML and hoping.

Every entry in a table

Browse a collection as a table, sort it, then click straight into any record — no folder archaeology.

Media in your bucket

Drag images in; they go to your own S3-compatible storage and a Markdown link is pasted for you.

Git at the core

Content stays as Markdown files in a repository, ready for a static site generator, a CI job or your own API.

Roles that make sense

Viewer, editor, admin and owner — explicit invitations, no surprise access, no shared root password.

How it works

Model it. Write it. Browse it.

  1. 01

    Define a schema

    Add a YAML schema to a collection: field names, types and which are required. One file, reviewed like any other.

  2. 02

    Write the entry

    Fill the fields through the frontmatter panel, then write the body in Markdown with the same editor as everywhere else.

  3. 03

    Browse the collection

    See every entry in a table, filter to what you need, and open a record. Everything is still a file in the repo.

Pricing

Start free. Stay as long as it earns its keep.

Every plan writes plain Markdown. Paid plans add scale, git sync and your own storage.

Billed monthly. Cancel anytime.

Free

For a first notebook and a first song.

$0/forever

Start free
  • 1 workspace
  • Up to 100 files
  • 3 collaborators
  • Markdown editor with live preview
  • Export to Markdown & HTML
  • Desktop & mobile apps
Most popular

Pro

For people who write every day.

$9/month

Choose Pro
  • 5 workspaces
  • Unlimited files
  • 10 collaborators
  • Git sync to your own repo
  • Custom S3 storage
  • Everything in Free

Team

For a content or worship team.

$29/month

Choose Team
  • Unlimited workspaces
  • Unlimited files
  • Unlimited collaborators
  • SSO / OAuth
  • Everything in Pro

Enterprise

For organisations that want their name on it.

$99/month

Choose Enterprise
  • Unlimited workspaces
  • Unlimited files
  • Unlimited collaborators
  • White-label branding
  • SSO / OAuth
  • Everything in Pro

Prices in USD. Your files stay yours on every plan — including the free one.

FAQ

Questions, answered.

No dark patterns, no “talk to sales” maze. If something is still unclear, the free plan is the fastest way to find out.

Start free
Where do my notes actually live?

Every note is a Markdown file in your workspace. On Pro and above, the workspace is pushed to your git remote on a schedule, so the same files exist in your repo. Any file can also be exported to Markdown or a standalone HTML page.

Can I use Notes, CMS and Songbook together?

The app runs in one mode at a time — you choose it when you deploy your instance — and all three share the same editor, files, collaboration and sync underneath. Teams often run one instance for writing and another for their song library.

What happens if I stop paying?

Your workspace is not deleted. Premium features such as git sync and custom S3 storage stop at the end of the paid period, and the workspace continues on the Free plan's limits. You can export everything before or after.

Does it work offline?

The desktop app and mobile apps keep a local copy, so you can keep writing without a connection; changes merge back into the workspace when you reconnect. The browser app needs a connection to load, then keeps a local copy of your session.

Who can see my writing?

Workspaces are private to their members. Roles run from viewer to editor to owner, and invitations are explicit. If you self-host, the database, the collaboration relay and the git clone all live on infrastructure you control.

Can I self-host?

Yes. The repository builds one Docker image that runs the API, the collaboration relay, the sync worker and the static app server, alongside Postgres and Redis. Migrations and plan seeding are CLI commands on the same image.

Start with one schema

Structure it once.
Keep it as files.

The free plan needs no card. Every entry carries frontmatter from the first one, so your static site generator already understands the content.

Web · Desktop · Mobile · Self-hosted