Add-ons and Integrations

Changelog

json
{  "changelog": {    "enabled": true,    "autoGenerate": true,    "label": "Changelog",    "description": "Latest product updates and fixes.",    "maxEntries": 30  }}

Use changelog auto-generation when deploys or merged changes should produce a first-class updates feed instead of a forgotten markdown page.

Add-ons

json
{  "addons": {    "feedback": {      "thumbsRating": true,      "editSuggestions": true,      "raiseIssues": false    },    "ciChecks": {      "brokenLinks": "error",      "grammarLinter": "warning"    },    "previews": {      "enabled": true    }  }}

Integrations

json
{  "integrations": {    "segment": {      "writeKey": "seg_123"    },    "posthog": {      "apiKey": "phc_123"    }  }}

The integration payload is intentionally flexible. Keep secrets out of committed config where possible and inject them at deploy time if your workflow supports it.

Variables

json
{  "variables": [    {      "name": "api.base_url",      "type": "string",      "label": "API Base URL",      "defaultValue": "https://api.example.com"    }  ]}

Variables help you centralize repeated product values instead of hardcoding them across dozens of pages.

Component theming

json
{  "componentTheme": {    "defaultVariant": "outlined",    "radius": "12px"  }}

Use this only after you have settled on overall theme, colors, and typography. It is a fine-tuning layer, not a substitute for good IA.