Public roadmap
What we're building
The Community Edition roadmap, live from GitHub. Items move as work ships — nothing here is a promise with a date.
Now
In progress on Community Edition.
- Content#{number}
Persist custom content types and fields
Admin → Content Types currently edits types in the browser only. They are not stored in the database or exposed on the API, so custom types cannot survive a reload or drive the…
- Platform#{number}
Public content REST API and OpenAPI for headless use
The website promises a typed headless CMS. Plugin authors have @justflows/sdk; frontend consumers still need a stable, documented public content API.
- Content#{number}
Built-in SEO: titles, canonicals, sitemap, and robots.txt
A complete website out of the box needs discoverability without a plugin.
- Developer experience#{number}
Plugin and theme author documentation
The runtime and SDK exist; authors still need a single path from hello-world to a signed-off .jfpkg.
- Developer experience#{number}
CI quality gate for core packages
Public CE needs a predictable merge bar: lint, typecheck, and tests on every PR into developers.
- Platform#{number}
Admin accessibility pass
The admin is the product for authors. Keyboard paths, names, and contrast should meet a WCAG 2.2 AA bar on the primary flows.
Next
Queued once the current slice lands.
- Extensions#{number}
Hosted marketplace catalog for community packages
Admin → Marketplace already has a UI. Site owners still need a real catalog of reviewed plugins and themes, not only local .jfpkg upload.
- Extensions#{number}
First-party Forms plugin
Forms already have an admin UI intended to live behind a plugin. Contact forms are table-stakes for a WordPress-class site.
- Extensions#{number}
First-party privacy-friendly Analytics plugin
The analytics admin page already expects a justflows.analytics plugin. First-party, on-site analytics matches the “no paid add-on” story.
- Platform#{number}
Content webhooks
Headless and integration users need push, not only poll.
- Content#{number}
Locale-aware content routing
Languages can be added in the admin. Content still needs locale fields, URL prefixes or domains, and a language switcher that themes can render.
- Platform#{number}
Redis cache adapter
Tools already exposes a Redis URL in cache settings. Multi-instance deploys need a shared cache, not only memory or filesystem.
- Operations#{number}
Backup and restore from admin Tools
Self-hosters need a supported way to snapshot content, media, and config without raw SQL.
Later
On the horizon, not scheduled.
- Developer experience#{number}
Stable SDK compatibility policy
v1.0 means plugin and theme authors can trust the public surface.
- Extensions#{number}
Plugin signing and install trust
A WordPress-class installer is a supply-chain surface. CE should make provenance optional at first, then expected for catalog packages.
- Platform#{number}
Role and capability editor in admin
Capabilities exist in code. Site owners still need to create roles and assign capabilities without a plugin.
- Platform#{number}
First-class multi-site
The schema already has sites. Operators running many properties on one CE should get a supported admin model.
- Platform#{number}
Static / edge export
The product story includes edge-ready rendering. A supported static export (or incremental static generation) lets high-traffic public pages leave the Node origin.
Shipped
Already in Community Edition.
Nothing in this column yet.
This page reads the public Justflows GitHub project. Columns can change without a release date attached.
Ready to flow?
Join the open-source community building the future of content platforms.