Roadmap
What is being worked on
Every open milestone in every repository, grouped by the four stages of the path. Nothing on this page is written by hand: closing a milestone removes it, closing an issue moves a number, and neither needs anyone to remember. A roadmap with typed dates is the fastest thing on a site to go stale, and it sits exactly where you decide whether a project is alive.
296 open issues across 4 repositories, read at build time
The API. Content types defined at runtime, the event log, the permissions.
Delivers rckoronadal.org on the stack (#722), train 1 of the roadmap review: D22 (#795), tenant domains (#792), site settings (#793), Pages (#718), Forms (#720, #845), choice fields (#803), rate limits as configuration (#823), the site kit (#721). Also carries everything that was 4.1.1, folded in on 14 September 2026 because master already held 4.2.0 API: the security fixes (#608, #638, #639, #640, #650, #653, #765), #599, and the licence change for modules (#816, #817). Pairs with barakoBrew 1.3.0 and barakoPress 0.4.0 and 0.5.0.
48 of 65 closed
Train 2, open the café. baryo.dev as a tenant (#794) with delivery caching (#549, #560, #561, #550, #508), the client libraries barista stands on (#182, #183, #186, #187, #631, #188), config as code (#345), barista up (#844), off-host backups (#780) and a lighter image (#746, #747). Pairs with barakoPress 0.6.0, barakoBrew 1.4.0 and BaryoVM 0.4.0.
5 of 57 closed
Train 3, workflows that chain, and barakocms.com as a tenant (#722). Step outputs (#575, #576), placeholders (#805, #828), email templates and attachments (#829, #806), required fields on transitions (#809), links in emails (#840), the schedule trigger (#839), sweep steps (#835), messages to outside services and their registry and starters (#831, #833, #834), job and run reliability (#106, #527, #528, #612, #663, #664, #694, #695, #696, #699, #700, #702, #703, #671, #655, #692), the Wolverine decision (#687) and barista errors (#851). Pairs with barakoPress 0.7.0 and barakoBrew 1.5.0.
1 of 53 closed
Train 4, business systems. Computed fields and rollups (#836), reports (#837), payments (#838), uniqueness per state (#830), row rules through a reference (#827), booking availability (#847), newsletter (#846), money with currency (#581), holds and numbering (#580, #584), documents (#585, #578), OAuth client credentials (#574), secrets from a store (#785), and the Color Me Fun gaps (#802, #804, #807, #808, #810, #811, #812, #813). Pairs with barakoPress 0.8.0 and barakoBrew 1.6.0.
0 of 24 closed
Train 5, field and scale. Offline capture and sync (#849), telemetry (#848), events across instances (#566, #787), tracing and correlation (#691, #624), read replicas (#564), partitioned retention and vector search (#621, #622), Azure Blob files (#728). Pairs with BaryoVM Azure and AWS targets and the VS Code extension preview (#843).
0 of 11 closed
The portal and what stands on it. 4.0 ships the one-way doors it needs.
6 of 28 closed
The console. Where editors write, model types, manage roles and run workflows.
Train 1: the console side of rckoronadal.org (BaryoDev/barakoCMS#722). Site and Theme screens (#134), the pages tree (#91), the block editor (#90), choice fields (#136), the binding picker (#140), and the MIT licence (#135). Everything else moved to 1.4.0 on 14 September 2026. Pairs with barakoCMS 4.2.0 and barakoPress 0.4.0 and 0.5.0.
24 of 27 closed
Train 2: the console catches up. Content types and entries as cards or a list with a writing editor (#138), module screens from the API descriptor (#46), the entries filter bar (#10), the form renderer (#5), tenant switcher (#15), analytics (#14, #51), the action library (#50), webhook workflows (#87), the workflow builder (#13), image field editor and files (#122, #132, #133). Pairs with barakoCMS 4.3.0.
0 of 22 closed
The 2026 redesign, its three open decisions, the library adoptions it needs, and the new surfaces (portal, chat panel, public pages). Nothing here starts before the decisions in #16, #18 and #55 land.
0 of 19 closed
The site engine. It reads your type names and field names rather than its own.
The foundation for configured sites (BaryoDev/barakoCMS#722): one renderer for many domains with identity and theme per request (#20, covering #14), pages and navigation (#4), any collection (#5). Pairs with barakoCMS 4.2.0.
9 of 9 closed
Delivers rckoronadal.org (BaryoDev/barakoCMS#722): block library v1 (#21). Pairs with barakoCMS 4.2.0 and barakoBrew 1.3.0.
0 of 10 closed
Delivers baryo.dev (BaryoDev/barakoCMS#722): block library v2, motion and outside data (#22). Pairs with barakoCMS 4.3.0.
0 of 7 closed
Delivers barakocms.com (BaryoDev/barakoCMS#722): docs as a collection (#23) and block library v3 (#24). Pairs with barakoCMS 4.4.0.
0 of 3 closed
After the three sites: plugin packages (#25), operator blocks (#26), viewer sessions (#7) and the visual editor (#9).
0 of 4 closed
The deploy CLI. Agentless deploys to VMs you own today, Azure and AWS next, plus hardening for the host.
Shipping now: the work merged since v0.2.1, plus a Homebrew tap and an install story that does not assume a Go toolchain.
10 of 10 closed
Bugs found in real deploys that should not wait for a feature release.
8 of 8 closed
The JSON surface becomes a contract, so an MCP server, an app or a cron job can drive it safely. Plus the docs that make the tool learnable.
1 of 28 closed
Design-led work: the nouns, the screens and the safety features that need a decision before code.
0 of 23 closed
How to read a big number
A milestone holding a lot of open issues is a bucket, not a plan. Work is filed against the release it is not blocking, so the far milestones collect anything that is real but not next. The nearest milestone for each product is the one being worked.
There are no dates here on purpose. This is one person and whoever else turns up, so a date would be a guess presented as a commitment.