Entities as the content layer
Model articles, navigation, catalog copy, and help text as governed multilingual entities rather than through a parallel content API.
Product / Deliver content
Documents
Turn governed multilingual content into stored files, PDFs, and email sent under your own identity.
Functions and workflows can render localized templates to PDF, store the generated file, and pass it to email delivery as an attachment.Verified 2026-08-20 · owner GSB Core · evidence ↗
One language context
The selected language is carried on tenant requests and reused for content, template bodies, translated subjects, and workflow output.
Templates bound to data
Reusable HTML templates render from entity, workflow, contact, and parameter data instead of documents assembled in application code.
Your sender identity
The platform provides template storage, rendering, PDF generation, attachment assembly, and delivery logs; the tenant registers and controls its own SMTP or SES credentials.
Operations
Each entry links to its reference page, generated from the same documentation the CLI and the MCP server return.
Keep reading
The guide covers the working shape of this capability, including request payloads, limits, and failure handling.
Rest of the platform
Database ↗
Query and transactionally save related data through one permission-aware entity contract.
Auth ↗
Enforce identity, tenancy, and record-level authorization at the data layer instead of in the interface.
Functions ↗
Add tenant-resident logic and shared libraries where data operations are not enough.
Workflows ↗
Describe durable, inspectable processes instead of hiding state in glue code.
Assistant ↗
Give a coding agent the same contract as your team, bounded by the same permissions.