One Studio, Many Publications

A product team may run a company journal, an engineering publication, a research notebook, and a customer education hub. They share an editorial practice, but they should not be forced into one site configuration or one content directory.

pr3sso Studio is designed to connect multiple publications while keeping each repository independent.

Connect repositories, not opaque workspaces

Editors sign in with GitHub and choose which accessible repositories to connect. Before a repository appears in the studio, pr3sso verifies that it is a valid publication and that the signed-in account has the required content permission.

The check looks for a valid pr3sso configuration, the expected Next.js application, and a readable metadata index. This makes the connection explicit and prevents the studio from treating an unrelated repository as a publication.

Repository access is scoped to publications the editor chooses. The GitHub access token remains in the encrypted server session rather than being returned to the browser.

Let each publication define itself

The root pr3sso.config.json file acts as both configuration and a clear repository marker. It tells the studio and the public application how that publication works.

Each repository can define its own:

• publication name, title, description, domain, and locale
• theme and home page mode
• default author and editorial language
• content, post, index, and conversation paths
• header links, archive page size, and article sidebar behavior

When an editor switches publications in the studio, these defaults switch with it. There is no global setting that silently overwrites a publication's identity.

Keep content histories separate

Every draft is committed to the repository selected in the studio. The post files, metadata index, conversation records, and Git history stay with that publication.

This boundary is useful for more than organization. Teams can give different people access to different publications, deploy sites independently, apply different review rules, and move a publication without exporting it from a proprietary content store.

Share the workflow without flattening the brands

pr3sso creates consistency where consistency helps: the drafting experience, validation rules, content model, and status workflow. It preserves variation where variation matters: voice, visual theme, domain, taxonomy, ownership, and release cadence.

One studio can therefore support a family of publications without turning them into one generic site. Editors get a familiar workspace, and every publication remains a self-contained product with its own source of truth.