Meet pr3sso: A Git-Native Publishing System

Publishing software often forces editorial teams to choose between a friendly writing experience and an engineering workflow they can trust. pr3sso is designed to keep both.

pr3sso is a Git-native publishing system for teams that want to develop ideas with AI, review every detail, and release structured content through their own repositories. It pairs a focused editorial studio with a fast public publication. GitHub remains the durable source of truth between them.

One product, two focused surfaces

The public publication is built for readers. It turns structured MDX posts into a fast archive with article pages, categories, tags, search, RSS, a sitemap, and share-ready metadata.

The studio is built for editors. It connects to one or more pr3sso repositories, provides an AI-assisted workspace for developing drafts, and manages each post from draft to publication.

These surfaces share the same content model, so an editor does not have to copy work from a writing tool into a separate CMS.

Your repository stays at the center

Every pr3sso publication owns its configuration and content. The repository defines the site identity, domain, theme, default author, language, content paths, and publishing behavior.

Posts remain readable files rather than records hidden inside a vendor database:

• MDX contains frontmatter and the article body.
• A metadata index powers archives, search, taxonomy, feeds, and sitemaps.
• Git history records when content changed and who changed it.
• The same files can be reviewed, backed up, migrated, or extended with familiar tools.

This structure gives editorial work the same traceability that engineering teams already expect from code.

AI assists; editors decide

Inside pr3sso Studio, an editor can begin with a rough idea, explore it in conversation, or ask for a structured post proposal. The result is not published automatically. Title, excerpt, taxonomy, SEO fields, and body remain visible and editable before the draft is saved.

pr3sso supports multiple model providers, including a Codex connection that can use the editor's current account. The model helps create momentum, while the product keeps the editorial decision with the person responsible for the publication.

A calm path from idea to release

pr3sso is built around a simple promise: the path from conversation to published page should be clear, inspectable, and reversible.

That promise shapes the entire product. The studio narrows attention to the draft in progress. Validation catches malformed or unsafe content. GitHub records the result. The public site shows only posts that have explicitly reached the published state.

The outcome is a publishing system that feels light to use without treating content operations lightly.