Roadmap
What's next, and in what order
The developer half shipped in v0.1.0. Everything an editor touches comes next, and the order is set by one goal: running this site on TachyonCMS itself.
Works today
Content types defined over the API or kept in a JSON file you diff and apply. Twenty-odd field types, including relationships, groups, arrays and map points. Filters that reach through relationships and into lists, joins, and select and populate so you fetch only what you need. Sign-in with sessions or bearer tokens, scoped API keys, roles, and access rules down to a single field.
That's v0.1.0, and it's pre-alpha. The README has the full list, with examples.
Being built, in this order
Rich text and blocksUnder way
Long-form writing with code samples and tables, and pages built from reusable sections.
Drafts, versions and scheduled publishing
So nothing goes live before it's meant to.
Media
Upload once, reuse anywhere, with responsive images.
Live preview
Look at a draft before it's published.
Authoring tools
Markdown in and out, and bulk import.
After those comes the admin screen. The bar for it: anyone who has used WordPress can pick it up without training. Here's what it's being built on.
None of this is in v0.1.0, and none of it has a date. What you're looking at is the order.
Think the order's wrong?
I'd much rather hear it now than after it ships. Two polls are open, and the roadmap itself started as a discussion you can reply to.
- Vote on what comes nextDrafts, media, live preview, Markdown import, the admin or GraphQL: which do you need first?
- Pick the first starterAstro, Next.js, SvelteKit, Nuxt, Remix or React Router, or something else. The winner gets built first.
- Reply to the roadmapDiscussion #35, where this page started.
Rather build than vote? I've opened a set of issues that are ready to pick up. Each one says which files to change, how to test it, and when it's done. Say you're taking one, and it's yours.