From Conversation to Commit with pr3sso Studio
See how pr3sso turns an early idea into reviewed MDX, complete metadata, and an atomic GitHub commit.
The hardest part of publishing is rarely typing the final paragraph. It is carrying an idea through exploration, structure, review, metadata, and release without losing context along the way.
pr3sso Studio keeps that work in one continuous flow.
Begin with the shape of an idea
An editor can start in conversation mode when the subject is still uncertain. The AI acts as an editorial partner: it can test an angle, identify missing evidence, propose a useful structure, or help separate one broad topic into several focused posts.
When the direction is ready, the editor can turn the conversation into a draft. A direct drafting mode is also available for ideas that already have a clear brief.
The studio supports OpenAI, Anthropic, Google, and Codex connections. Provider choice is separate from the publication itself, so teams can use the model that fits their workflow without changing the content format.
Review the complete post, not just the prose
A publishable article is more than its body. pr3sso produces a structured proposal that keeps every important field visible:
- title and canonical slug
- excerpt, author, and locale
- categories and tags
- featured status and cover image
- SEO title and description
- safe Markdown content
The editor can revise these fields in the draft preview before saving anything. The canonical slug is regenerated from the title, which prevents links and titles from quietly drifting apart.
Save one consistent snapshot
When an editor saves a draft, pr3sso writes three coordinated records:
- The MDX file containing frontmatter and the article body.
- The metadata index used by the public site.
- The conversation record that preserves how the draft was developed.
All three are written to the selected GitHub repository in one atomic commit. If validation fails, the operation stops before a partial content state is created.
This matters because the public site depends on agreement between the MDX source and the metadata index. By committing them together, pr3sso keeps search, archives, feeds, and article routes aligned with the content an editor reviewed.
Publish with an explicit state change
Saving a draft does not make it public. The Posts workspace shows the content library and its status. Editors can publish a draft, archive a published post, or restore an archived item.
The public application exposes a post only when its status is published and it has a publication timestamp. The article route, search results, RSS feed, and sitemap all use that same rule.
The result is a workflow with useful automation and a deliberate release boundary. AI accelerates the work. The editor approves the artifact. Git records the change. The publication renders only what has been intentionally released.