ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

The manual's PDF pipeline: live SQL grids, diagrams, form mockups, no server

Documentation pages render to PDF with live SQL grids laid out as on the web, Mermaid and sequence diagrams as embedded SVG, and application forms drawn as mockups from markup. A script renders a page or a book.

A manual that lives in the product must also leave it: as a PDF a customer can file, with the same grids and diagrams the web page shows. This release gives the documentation engine that pipeline.

What renders

  • Live SQL grids Database, grid and tab elements are pre-processed on the server, engine icons and dialect translations included, before the stylesheet runs, so the PDF matches the web layout.
  • Diagrams Mermaid and sequence diagrams are rendered to SVG by the microservice and embedded as vector graphics.
  • Forms as mockups A form element with toolbar, tabs, panels, fields, alerts and buttons draws an application form in HTML and PDF instead of a screenshot that goes stale.
  • Charts The documentation chart renderer moved to Chart.js with a converter for the previous library's options and a visible fallback for unsupported series.

Without a server

  • A render script turns a page or a whole folder into PDF with a validator, an XSLT processor and the formatting engine, and a helper injects intrinsic SVG sizes so diagrams fit their height.

The same source now serves the manual in the product, over MCP to agents, and as a book.