Use markdown and Jupyter notebooks in doc pages - #548
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 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. 🚀 New features to boost your workflow:
|
|
@will-moore this would be my take on how I'd structure the docs going forward. I essentially broke all the examples from the |
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.
f3949eb to
491ef9a
Compare
|
Could you add info to the main |
|
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? 🤔 |
|
@will-moore Also, I just realized: PR builds are already enabled 😅 Just hit the link in the actions: |
|
Not necessarily related to this PR but a few points by looking through the webpage:
|
docs: ome-ngff -> ome-zarr
8ac9c15 to
3bc81a5
Compare
|
Thanks for the feedback! @joshmoore I added a markdown document with the validator embedded as an 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? 🤔 |
|
@will-moore anything you think I should add here? |
Yep and I think it kind of makes sense. If Edit: In the future, I could imagine that the |
for more information, see https://pre-commit.ci
|
@will-moore build is looking green on my end so all cross-references seem to resolve correctly 👍 |


Fixes #536