M-Press Studio plan

A clear boundary between the local open-source core and the hosted authoring service.

What Studio is

M-Press Studio is the optional hosted layer for teams that want shared control of documentation without giving up the local-first M-Press workflow. The free binary remains the complete static generator. Studio does not lock a site to a server and it does not change Markdown into a proprietary format.

The first Studio release

The first paid release should solve the work that is difficult to share or retain locally:

• private project workspaces with GitHub authentication and team roles;
• deployment history for Cloudflare Pages and Netlify, including previews, approvals, rollback, and environment secrets;
• retained Lighthouse, link-check, build-timing, and accessibility reports;
• privacy-aware analytics with an explicit consent and retention policy;
• shared translation memory, review assignments, budgets, and audit history;
• managed version artifacts with retention and release promotion;
• a hosted M-Press Studio editor that can hand work back to a normal Git branch.

What stays open source

Local Markdown and HTML authoring, every documented component, the theme, search, reader accessibility controls, translations through a local provider or API, version capture and verification, checks, Lighthouse audits, ZIP export, Cloudflare and Netlify deployment, and the generated static site all stay in the open-source project. A team can leave Studio and keep building the same site.

Delivery sequence

1. Stabilise the open-source contract: settings, forms, images, translations, deployment, versions, caching, and browser conformance.
2. Add a small Studio service for account, project, and deployment history.
3. Add retained quality reports and privacy-aware analytics.
4. Add shared translation and version workflows only after the local formats are stable and exportable.
5. Add collaboration and editor affordances without changing the Markdown source format.

The commercial test is simple: Studio must save a team time or provide shared history and analytics. It must never be required to generate or host a site.