[PLACEHOLDER] This stub documents the notebook → page workflow. No real notebook is included. Replace with real content (or a real .ipynb) when ready.
Authoring a project page from a .ipynb
Quarto can render a Jupyter notebook as a page exactly like a .qmd. Two common approaches:
Option A — render the notebook directly
- Put
your-project.ipynb in this folder (give it a YAML raw cell at the top with title, date, categories, description, image).
- Add it to the navbar/listing the same way
.qmd pages are added. A notebook in a project folder is picked up by the Projects listing automatically.
uv run quarto render executes it through the venv’s Jupyter kernel; the cached output lands in _freeze/.
Option B — keep the notebook, author the page in .qmd
Author the page as index.qmd and pull figures/results in from a notebook you run separately (e.g. export a Plotly figure or a PyVista scene). This keeps prose and heavy computation cleanly separated.
Trade-offs. A .qmd gives the cleanest diffs, full control over layout, and easy mixing of prose, math and raw HTML (e.g. the PyVista iframe). A .ipynb is convenient when the analysis already lives in a notebook, but notebooks produce noisier diffs and mix narrative with execution state. For this site, prefer .qmd for write-ups and reserve notebooks for analysis-heavy pages.
See the reference stub for the math, Plotly and PyVista-embed patterns.