Engine + Framework

SeqDiag with Lit

Integration guide for teams shipping diagram rendering in Lit.

SeqDiag usage guidance

Best for

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

Syntax tip

Keep SeqDiag source deterministic and reusable across environments.

Quick start

Call the ChartQuery API from your Lit stack and return rendered SeqDiag output to the UI.

Recommended flow

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

Typical Lit integration path: /server/diagram-renderer

SeqDiag integration details

FieldValue
EngineSeqDiag
FrameworkLit

Lit implementation checklist

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

SeqDiag source example

// SeqDiag source
// Add your diagram content here

SeqDiag in Lit: quick comparison

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

Feature
Lit 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 SeqDiag in Lit 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