Solutions library
Match GPDoc to specific work: publishing, browser notebooks, technical papers, presentations, private docs, and source-controlled review paths.
Move approved docs, papers, and hubs from source files to static output.
Pair lessons, notebooks, slides, and review notes in one workspace.
Build technical slides from diagrams, code, tables, and narrative docs.
Keep sensitive work in local-first files with deliberate sync and exports.
Each page maps an audience or workflow to concrete GPDoc files, review steps, exports, and setup docs.
Edit one open file with connected presence, labeled cursors, comments, suggestions, and review controls across supported GPDoc surfaces.
Build reports, presentations, notebooks, diagrams, and handoff material in open, versionable files with review history.
Build reviewable lessons from documents, slides, browser notebooks, code, diagrams, and published pages without splitting the source across separate authoring tools.
Keep sensitive Markdown source on organization-managed storage, review changes in open files, and connect remote services only when the workflow requires them.
Keep launch briefs, release notes, presentations, and website copy in open, versionable files that product, engineering, and go-to-market teams can review.
Export HTML or use GPDoc's GitHub Pages workflow to share a supported document as a website while keeping the working source open and versionable.
Use attributed comments and suggested changes from people and configured agents without converting the accepted document into a proprietary review format.
Keep Python or JavaScript and TypeScript code, captured output, and technical explanation in one GPDoc notebook, then export an open copy for review or reuse.
Build Markdown-based presentations with Mermaid diagrams, LaTeX math, code, tables, review history, and open export paths.
Draft technical papers in Markdown with LaTeX math, code, diagrams, tables, and supporting browser notebooks, then export a reviewed copy.
