Markata v0.15.0 takes its rendering engine beyond the static-site build. Python applications can render Markdown through a documented API, while Go and browser workbenches make the same expressive authoring experience available in local tools and offline-capable editors.
Bring Markata rendering to more places #
The Python renderer exposes synchronous and asynchronous APIs for HTML, feature signals, and ordered assets. A native Go workbench provides local editing and preview; a WebAssembly workbench can render in the browser without a rendering service. Python and Go editors also connect to Markata LSP for context-aware completions.
These integrations share a common direction while keeping their security, asset delivery, and offline behavior explicit. The browser workbench can run without a rendering service after its assets are available; that does not mean every rendered site is fully offline.
Make Markdown more expressive #
Charts gain accessible data disclosures and static fallbacks. New layout, icon-card, status, gauge, checklist, and source-preview primitives help authors communicate information directly in Markdown. Roads and story layouts support clearer timelines, while improved palette behavior and typography make rendered pages easier to read.
The CLI, agent setup, and editor workflows also receive usability and reliability improvements.
Upgrade #
Download the v0.15.0 release, or install the Go command with:
go install github.com/WaylonWalker/markata/cmd/[email protected]
This is a 0.x release. The markata executable is preferred and markata-go remains available. Existing markata-go.toml, [markata-go], and MARKATA_GO_* configuration continue to work. The new Python rendering API is an integration for applications, not compatibility with the original Python plugin system.
See the v0.14.0 to v0.15.0 comparison, the Python renderer guide, Go workbench guide, and WASM workbench guide.