Page views, custom events, sessions and funnels, with every event carrying the entry, revision and release it happened on. myna analytics impact compares equal windows either side of a release: per entry, per event, and the reports filed since.
Reporters file and follow their reports inside your own product, with an identity your backend signs. Ingest keys scope to a project and rotate with a grace window, and the people who report are a surface you can filter, read and moderate.
A project declares which Myna products it runs. Feedback collects bug reports, QA findings and suggestions with the context needed to reproduce them, and myna_get_report hands an agent the description, environment, evidence and conversation in one call.
myna api calls any management route with the credential the CLI already resolved. myna mcp install and myna skills install configure coding agents in one command. An ast_ id counts as a reference wherever it appears in an entry, including inside a body.
Add a passkey from account settings and sign in with your fingerprint, face, or security key instead of going through GitHub. Approving a CLI login or an MCP connector now asks you to confirm it is you, since both hand out access that outlives the session granting it.
Reads can be pinned to a numbered release, so a build takes content as a version rather than as whatever the API returns. myna.lock records the pin, and connecting a repository makes publishing open a pull request that moves it.
Reading an entry now tells you who else is already editing it: every open change set staging it, the fields each one touches, and where more than one collides. The conflicts check reported the same thing, but only at publish.
Collections declare the rules they refuse to publish against, in schema-as-code next to their fields. The built-in check suite drops to publish preconditions: SEO and alt-text are now policy you opt into. myna update upgrades the CLI in place.
Change-set diffs carry word-level segments for prose fields. Images get a perceptual hash, so a resized copy is found as a duplicate. A new access check says why a call was refused, and myna schema pull --open-pr turns schema drift into a pull request.
Every publish is a numbered release, and reverting one drafts a change set that restores the state before it. Several change sets can hold the same entry, and the ones that lose the race rebase.
Content checks run automatically when a change set changes, and appear as pending before they do. Custom checks get a settings screen, and published reads got faster.
Entries are searchable, change sets have a field-level diff, and API keys can be confined to specific collections. Checks can come from outside Myna and block publishing, and images are resized on delivery.
Myna hosts an MCP server at api.myna.sh/mcp. Connect with a URL and an OAuth approval: nothing to install, no key to paste, and no publish permission by default.
@myna-sh/react ships hooks over the public content client, and joins the lockstep release set alongside the SDK, CLI, and MCP server.
Preview reads compose a change set over published content, so a list page in preview renders the whole site. Collections can carry an editorial order.
The documentation site is live. Every page is available as HTML, as raw Markdown, and through llms.txt. Reference pages are generated from the code.
Change sets take assigned reviewers, approvals, field-level comments, automated checks, and a publish time.
