Engine + Framework

Structurizr with Marko

Integration guide for teams shipping diagram rendering in Marko.

Structurizr usage guidance

Best for

  • General diagram rendering
  • Programmatic documentation pipelines
  • Automated visual generation

Syntax tip

Keep Structurizr source deterministic and reusable across environments.

Quick start

Call the ChartQuery API from your Marko stack and return rendered Structurizr output to the UI.

Recommended flow

  1. Store your Structurizr source in code or markdown.
  2. Send source to a server-side endpoint backed by ChartQuery.
  3. Render returned SVG/PNG in Marko pages and docs.

Typical Marko integration path: /server/diagram-renderer

Structurizr integration details

FieldValue
EngineStructurizr
FrameworkMarko

Marko implementation checklist

  • Add a server-side rendering endpoint
  • Validate and sanitize diagram input
  • Cache rendered output for recurring requests

Structurizr source example

// Structurizr source
// Add your diagram content here

Structurizr in Marko: quick comparison

Why teams usually prefer the ChartQuery API pattern over direct client-side rendering for Structurizr in Marko.

Feature
Marko native setup
ChartQuery API setup
Server-side rendering without browser dependencies
Unified output (SVG/PNG) for docs, dashboards, and emails
Consistent rendering across environments
Works with CI/CD pipelines
Fits backend-first architectures
Single rendering workflow across multiple frameworks

Ship Structurizr in Marko faster

Use ChartQuery to standardize diagram rendering across your stack with one API, one workflow, and predictable output quality.

Get started with ChartQuery

Start generating charts today

No API key required to get started. Generate charts, diagrams, and more with a single HTTP request.

Get StartedView Pricing