v0.2.0 is out. Grab a binary for Linux or macOS, or the Docker image. Read the release notes

The admin

An admin anyone can pick up. It isn't built yet.

TachyonCMS is an API today. The admin comes next, held to one test: someone who has only used WordPress picks it up without training.

On the roadmap

What’s true today

There’s no admin screen in v0.2.0. You manage content types, users and documents over HTTP or with the tachyon command, and that’s the whole interface. I’d rather say so here than show you a mockup and let you guess.

The test it has to pass

Someone who has only ever used WordPress should be able to sit down and run a site with it, without training: adding a content type, writing a post, scheduling it. If that person needs a manual, it isn’t finished.

What’s already underneath

Some of the admin’s groundwork ships today, because it lives in the schema:

  • Rows, collapsible sections and tabs decide how fields will sit on the editing screen, without changing your data.
  • Every field can carry a description, a placeholder, a place in the sidebar or a condition for when it shows.
  • GET /api/access tells each person what they may do, so the admin can hide a button rather than let it fail.

What comes with it

Sign-in, API keys and access rules shipped in v0.1.0, so the admin will have something to sign in to. Blocks and rich text shipped in v0.2.0, so it will have pages and posts to edit. Before the admin itself come drafts, versions and scheduled publishing, then media, live preview and authoring tools: pushing and pulling content as Markdown files, and bulk import. The admin follows those.

There are no dates yet. The roadmap shows the order.

Where this comes from

Every claim on this page comes from one of these. If one's out of date, tell me in an issue.