M-Press Pro

M-Press Pro adds the features that need a server, persistent data, or shared state. Your documentation stays Markdown. Your site stays fast and portable. Pro supplies the managed service layer behind it.

Use Pro when your documentation needs to do more than present static content:

• collect votes with polls and ratings;
• remember progress, preferences, and other reader state;
• receive feedback and form submissions;
• understand readers with privacy-aware analytics;
• publish through managed hosting with previews and rollback;
• protect private documentation and control access;
• coordinate translations, reviews, and releases across a team.

Static where possible. Stateful where useful.

M-Press does not turn the whole site into a web application. Pages still arrive as generated HTML. A Pro component connects to the service only when it needs to read or write data.

This keeps the normal advantages of M-Press: fast pages, simple deployment, accessible content, and a repository that remains the source of truth.

Add components that can remember

Static components explain information. Pro components can receive an answer, save it, and respond to it.

Use them for:

• polls, votes, ratings, and reader feedback;
• forms with stored submissions and notifications;
• checklists and learning progress that continue across visits;
• live status, release, and service information;
• authenticated content and reader-specific views.

The component belongs in Markdown with the rest of the page. Pro manages its data, validation, permissions, and service endpoint.

Learn what readers cannot find

Documentation analytics should answer documentation questions. Pro shows page traffic, search terms, searches with no results, navigation paths, language and version use, and reader feedback.

Privacy, consent, and retention are project settings. You do not need to add a general-purpose advertising tracker to understand whether the documentation works.

Host and publish the complete site

Connect a repository and let Pro build, preview, and serve the generated output. Each change can have a preview URL. A verified build can be promoted without rebuilding it, and a previous release can be restored when necessary.

Managed hosting includes custom domains, certificates, edge delivery, release history, and rollback. The generated site remains exportable.

Protect documentation when it is not public

Add sign-in and access rules without building an authentication system into the static site. Restrict a whole site, a version, or a section to the people who should see it.

Team roles and an audit history show who changed content, approved a release, or updated project settings.

Keep the workflow you already trust

Continue to write Markdown locally, run the development server, review the generated site, and build in CI. Pro coordinates only the work that needs a service or shared state. It does not replace the project or change the source format.

If your team leaves Pro, the repository and generated site still build normally.

Keep a quality history

A single green build is useful. A history shows whether the site is improving. Pro retains performance, accessibility, link, asset, and build results so you can see when quality changed and which release introduced it.

Translate and review as a team

Share translation memory, terminology, reviewer assignments, provider budgets, and approval state. Schedule translation work, track stale pages, and review changes before publication. Authors still work with the same source files and protected component structure.

Edit without surrendering the repository

The hosted editor gives contributors a guided way to update content, settings, and translations. Accepted work returns to a normal Git branch for review. Your repository, history, and generated files do not become trapped in a proprietary content store.