Where we're taking Primo next.
Four areas we're planning for Primo: multilingual sites, an extension system, content editing for existing apps, and better editing and publishing workflows. These describe the direction; scope and priorities may change as we build and hear what you need.
Multilingual sites / i18n
Build a site in multiple languages and give clients a way to manage each translation in context. The goal is translated content, locale-specific routes, language switching, and clear handling of content that hasn't been translated yet.
This work focuses on the languages of your website. Translating Primo's editor interface is a separate area.
Plugins & extensions
Add capabilities to a Primo site through a documented extension API, with support for custom fields and integrations. Installable plugins would make those capabilities reusable across projects and available through the marketplace.
The extension API and the first plugins are separate parts of the work. Forms, search, and analytics are examples of what we'd like developers to be able to add. Read more about plugins and join the waitlist.
Existing app integration
Add Primo's content editing to an app you already have. The initial direction is SvelteKit: keep your production components in your project and use Primo to manage content and give editors a visual editing surface.
We're also exploring how this could work with Astro and, further out, Next.js. Those paths need more investigation before we define their scope.
Editing & publishing
Give the people managing a site more confidence in everyday changes. We're exploring clearer edit history, ways to compare and restore earlier content, and undo for accidental edits.
We're also looking at workflows for sharing drafts for review, controlling who can publish, and scheduling content. The goal is to make it easier for clients and teams to review changes and decide when they go live.