Use default font for headings and body text

[willingc]

This PR uses the default pydata sphinx theme font for body text and headings.and leaves barlow for heading.

Addresses #88.

2025-02-27 docs workgroup meeting agreed that removing Barlow made sense. If needed, we can revisit the fonts in a future issue/PR.

[willingc]

[willingc]

If you wanted a commonly paired font with Barlow, this would be how the main test page looks with Roboto as text font.

IMHO I think the default provides the best readability.

[willingc]

@DragaDoncila @psobolewskiPhD @melissawm For your review.

[DragaDoncila]

Hmm CI is not happy 🥹

[willingc]

Blah, these unrelated to the PR seg faults concern me. @DragaDoncila can you restart the CI (I don't have sufficient permissions) to see if this is an intermittent seg fault or reproducible seg fault.

[willingc]

As an aside, I don't think it is necessary to run a complete build of the docs for every theme change. I think for most cases a representative set of pages would suffice.

[DragaDoncila]

@willingc re-ran!

[psobolewskiPhD]

CI here needs to be updated for the changes in napari/docs and napari/napari.

As an aside, I don't think it is necessary to run a complete build of the docs for every theme change. I think for most cases a representative set of pages would suffice.

Really good point. I put together the full build when we were first testing things with the theme and a new version of the upstream theme. But now that we arn't tinkering much, we could safely drop stuff -- like the gallery.

[willingc]

Seg faulted again but in a different place. I think that we still need to work through the seg faults but I don't think this is the repo to do that. I would prefer napari/napari to be the place to do so or possibly napari/docs as well. If it is ok with you, I can put up a PR in the morning to swap the workflow to building the example docs.

[psobolewskiPhD]

could also be the tensorstore constraints issue Grzegorz mentioned. lets see if my new PR passes.

[psobolewskiPhD]

@DragaDoncila @willingc The build passes when updated for the latest changes to the docs dependencies (just like napari/docs and napari/napari):
#186
I also used html-noplot to make it quicker.

[DragaDoncila]

I optimistically merged #186 and will merge into here to see if that works.

[DragaDoncila]

CI is green now yay 🎉 and I've had a scroll through different pages like the API ref, pages with lots of code and text pages, and this all looks good to me. Thanks @willingc ❤️

[TimMonko]

@psobolewskiPhD why 0.7 milestone?

[psobolewskiPhD]

@TimMonko we will need a release of this theme in order for it to be used by napari/docs.
(which also means we will need the constraints in napari/napari to be updated to allow it!)

[willingc]

@psobolewskiPhD A release of this theme shouldn't be difficult. Looking at the code in napari/napari, there are only 2 places where the config/constraints list napari-sphinx-theme (pyproject.toml and the docs constraints file). I'm not sure that all the constraints files need to be regenerated to use the theme. Thoughts?

[psobolewskiPhD]

I didn't mean to imply it was difficult, but a release of the theme and then a PR to update of constraints does need to be done to see the effect of any PRs to the theme.

[TimMonko]

I think me (and maybe @willingc ) assumed the 0.7 was tagged to the napari release milestone, but I've realized this is probably the sphinx theme milestone. Didn't realize the theme was a confusingly-close-to-napari 0.6.0

[psobolewskiPhD]

Oh, sorry! My b!
Yeah, exactly: 0.7.0 milestone is next theme release.

[willingc]

Thanks @psobolewskiPhD. Yep, I totally thought we were discussing the napari release. All good. TYVM, @TimMonko Thanks for clarifying too.