Publishing and exports

GPDoc’s export engine turns your structured content into the formats stakeholders need without manual cleanup.

Supported formats

Markdown for developer hubs and static site generators.
HTML microsites optimized for Netlify, Vercel, or on-prem hosting.
PDF handouts with preserved typography and accessibility metadata.
Jupyter (.ipynb) for researchers and educators who prefer native notebooks.

Automating exports

Configure workflows in workspace.config.json or through the UI scheduler:

{
  "exports": [
    { "collection": "docs", "format": "html", "target": "netlify" },
    { "collection": "slides", "format": "pdf", "target": "s3" }
  ]
}

Each run tags the resulting commit and posts status updates to Slack, Linear, or email via webhooks.

Preview before publishing

Generate preview URLs that render exactly like production. Stakeholders can review without cloning the repo, and approvals flow back into Git once complete.

Security note

Exports execute inside your infrastructure. Sensitive data stays private unless you explicitly publish it. Use branch protection rules to gate external releases.

Troubleshooting

If exports fail, run gpdoc export --verbose to inspect component validation errors.
Outdated assets? Clear the cache with gpdoc export clean before rerunning.
Need custom branding? Override Tailwind tokens in theme.config.ts and rerun the export.

With a few automation hooks, GPDoc keeps your content flowing to every channel without duplicate work.