Sharing browser notebooks

Typical notebook friction

The explanation and runnable example drift when they live in different files.
Learners can see an output without knowing which source or dependency produced it.
A static screenshot cannot be rerun or reviewed as code.

What GPDoc supports

Python through Pyodide for compatible browser-based Python work.
JavaScript and TypeScript cells through GPDoc's browser runtime.
Markdown, LaTeX math, tables, and Mermaid diagrams beside the code they explain.
Open exports to HTML, Markdown, LaTeX, or Jupyter .ipynb for the destination that needs the lesson.
Versionable source that can use a Git workflow when the notebook belongs in a repository.

Dependency boundary

Package support depends on the selected browser runtime. Record the runtime, packages, and versions required by the lesson, then test the exported notebook in its destination environment.

Suggested workflow

Start with a Markdown cell that states what the learner will run, what output to expect, and which runtime or package versions are required.

Use Python cells for Pyodide-compatible work or JavaScript and TypeScript cells for the GPDoc browser runtime. Keep sample data free of credentials and restricted information.

Execute the notebook from the beginning, inspect every output, and review the source changes before sharing it. Use Git review when the notebook is stored in a repository.

Export HTML for reading, Markdown or LaTeX for another publishing flow, or .ipynb for a compatible Jupyter environment. Review the exported copy separately from the GPDoc source.

What to verify

A new reader can identify the required runtime and dependencies.
The notebook runs from its first cell without relying on hidden local state.
The captured output contains no private data.
The exported file opens and runs as expected in the recipient's environment.

Review browser notebook runtime details, or check the complete export matrix.