Publish open documents as websites

Keep the source file separate from the published copy

Write and review the document in GPDoc or Markdown. When the content is ready, create HTML for a website destination. The source can remain in Git and continue through normal comments, suggestions, and version review.

Two supported paths

Export standalone HTML and add it to your existing static-site workflow.
Use the web app’s GitHub Pages publishing action for a supported document and authorized repository.

GPDoc does not claim to configure every static host, deployment pipeline, domain, analytics service, or localization workflow.

GitHub Pages workflow

Resolve the required comments and suggestions, then confirm the accepted content and links.

In the GPDoc web app, open the current file’s File menu and choose the GitHub Pages publishing action.

Select an authorized repository and the path shown by the publishing window. Repository permissions and branch rules still apply.

Open the final GitHub Pages URL after GitHub completes its deployment, then check the document layout, links, and public-data boundary.

Sharing boundary

Publishing makes the generated website available according to the repository and GitHub Pages settings. Remove private information, secrets, and customer data before publishing.

Other website workflows

If your team already uses a static-site generator or host, export HTML or keep Markdown in the repository and let that existing pipeline build the site. GPDoc supplies the source and supported export. Your repository and hosting configuration remain the deployment authority.

Review the exact publishing and export formats, or start building in GPDoc.