Skip to content

Use markdown and Jupyter notebooks in doc pages - #548

Merged
jo-mueller merged 18 commits into
ome:masterfrom
jo-mueller:glow-up-docs
Mar 19, 2026
Merged

Use markdown and Jupyter notebooks in doc pages#548
jo-mueller merged 18 commits into
ome:masterfrom
jo-mueller:glow-up-docs

Conversation

@jo-mueller

Copy link
Copy Markdown
Collaborator

Fixes #536

@codecov

codecov Bot commented Mar 10, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.83%. Comparing base (0fc60fd) to head (8c49daf).
⚠️ Report is 218 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #548      +/-   ##
==========================================
+ Coverage   86.80%   86.83%   +0.02%     
==========================================
  Files          14       14              
  Lines        1857     1861       +4     
==========================================
+ Hits         1612     1616       +4     
  Misses        245      245              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jo-mueller

Copy link
Copy Markdown
Collaborator Author

@will-moore this would be my take on how I'd structure the docs going forward.

I essentially broke all the examples from the python.rst file into separate jupyter notebooks that are actually executed on build 👍

docs: add myst outputs to ignored files

[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

docs: delete legacy markdown viewing tutorial

deps: add sphinx-design to doc deps

deps: add sphinx-book-theme to doc dependencies

[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

Delete write_hcs_plate.md

docs: fix link

docs: remove jupyter execute artefacts from tracked files

test: remove faulty notebooks from build

test: remove read notebook

Delete view_ome_zarr.ipynb

ci: push through errors

Revert "Delete view_ome_zarr.ipynb"

This reverts commit 7635186.

Revert "test: remove read notebook"

This reverts commit 49379c6.

docs: remove read notebook

ci: ignore false positives in codespell

do not show viewer

docs: delete view notebook

deps[docs]: Add ome-zarr-py to deps

deps[docs]: update local version

update deps

fix build

[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

Revert "docs: delete view notebook"

This reverts commit 93ff591.

[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

deps: add napari-ome-zarr to deps

remove view notebook

Revert "docs: remove read notebook"

This reverts commit 0be2723.
@jo-mueller
jo-mueller marked this pull request as ready for review March 11, 2026 21:50
@jo-mueller jo-mueller mentioned this pull request Mar 12, 2026
6 tasks
@will-moore

Copy link
Copy Markdown
Member

Could you add info to the main README or docs/README/ on how to build the docs locally?
And is it possible to have the docs deploy somewhere from a PR? (not essential, but nice)!

@jo-mueller

Copy link
Copy Markdown
Collaborator Author

@will-moore

And is it possible to have the docs deploy somewhere from a PR? (not essential, but nice)!

That'll have to be done by the readthedocs maintainers of the RTD project. If you have access there, you can add me as a maintainer under Setup > Maintainers. Otherwise, the respective setting is under Settings at the very bottom:

image

Could you add info to the main README or docs/README/ on how to build the docs locally?

Good idea!

@jo-mueller

Copy link
Copy Markdown
Collaborator Author

What I didn't get to work was to show how to use (napari-) ome-zarr in a notebook that would include a viewer screenshot - maybe there are some restrictions regarding notebooks executed on the RTD CI and GUI applications? 🤔

@jo-mueller

Copy link
Copy Markdown
Collaborator Author

@will-moore Also, I just realized: PR builds are already enabled 😅

Just hit the link in the actions:

image

Comment thread docs/source/howtos/build_custom_pyramid.ipynb Outdated
@joshmoore

Copy link
Copy Markdown
Member

Not necessarily related to this PR but a few points by looking through the webpage:

  • Generally some graphics would help, which leads me to wonder if we embed the validator and/or vizarr in various places
  • Left-hand menu: s/OME-NGFF/OME-Zarr/

docs: ome-ngff -> ome-zarr
@jo-mueller

jo-mueller commented Mar 13, 2026

Copy link
Copy Markdown
Collaborator Author

Thanks for the feedback! @joshmoore I added a markdown document with the validator embedded as an iFrame, that's actually pretty cool to use right out of the built pages :)

I also played with having napari screenshots directly here in the demo notebooks, but the RTD seems to have an issue with GIU applications in notebooks, as it seems. Or maybe it's the async rendering? 🤔

@jo-mueller

Copy link
Copy Markdown
Collaborator Author

@will-moore anything you think I should add here?

@will-moore

Copy link
Copy Markdown
Member

I'm seeing [] in a bunch of places:

Screenshot 2026-03-17 at 14 16 46

Ah - is this the output from the code above?

Comment thread docs/source/basic/write_image.ipynb Outdated
Comment thread docs/source/basic/write_image.ipynb Outdated
@jo-mueller

jo-mueller commented Mar 17, 2026

Copy link
Copy Markdown
Collaborator Author

Ah - is this the output from the code above?

Yep and I think it kind of makes sense. If compute=False is passed to the function, the writer will not execute but return a list of delayed objects. If compute=True, everything is written, all jobs are finished so the list is empty.

Edit: In the future, I could imagine that the delayed_objects becomes an attribute of the NGffImage class introduced in #515 In that case, we wouldn't need the return

@jo-mueller jo-mueller changed the title WIP: Glow up docs Glow up docs Mar 17, 2026
@jo-mueller jo-mueller changed the title Glow up docs Use markdown and Jupyter notebooks in doc pages Mar 17, 2026
@jo-mueller

Copy link
Copy Markdown
Collaborator Author

@will-moore build is looking green on my end so all cross-references seem to resolve correctly 👍

Comment thread docs/source/basic/write_labels.ipynb
Comment thread docs/source/advanced/build_custom_pyramid.ipynb Outdated
Comment thread docs/source/advanced/build_custom_pyramid.ipynb Outdated
Comment thread docs/source/explanation/multiscale_pyramids.md Outdated
@jo-mueller
jo-mueller requested a review from will-moore March 19, 2026 09:23

@will-moore will-moore left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thanks! 👍

@jo-mueller
jo-mueller merged commit aacce7b into ome:master Mar 19, 2026
13 checks passed
@jo-mueller
jo-mueller deleted the glow-up-docs branch April 10, 2026 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Give the documentation a glow-up?

3 participants