Setting up infrastructure for documentation and jupyterlite

[hoxbro]

This set up the infrastructure to build docs and jupyterlite in HoloNote.

The doc files are heavily inspired by Panel (with holoviews colors). I have left chunks commented out as they could be needed later and will, in the future, either be uncommented or removed.

The example files have been moved into a subfolder.

This introduces the following commands: hatch run docs:build and hatch run docs:server for building the docs, and hatch run lite:build and hatch run lite:server for building jupyterlite and launching the server.

The dev website of docs can be found here: https://holoviz-dev.github.io/holonote/ and the dev website of the jupyterlite can be found here: https://holoviz-dev.github.io/holonote-jupyterlite/lab/index.html

[codspeed-hq]

CodSpeed Performance Report

Merging #82 will not alter performance

_{⚠️ No base runs were found}

_{Falling back to comparing docs (968e255) with main (8d8132d)}

Summary

✅ 6 untouched benchmarks

[jbednar]

Nice!

[ahuang11]

Excited to see the docs :)

[maximlt]

I'm really unsure this file is used at all in the HoloViews build. Might wanna remove it here and see what happens.

[hoxbro]

I use it to create the reference manual pages.

[maximlt]

Since it's a new project, you may want to avoid having to build the docs with nbsite directly (to avoid a layer of indirection that often comes in your way, e.g. when you want to use something like sphinx-autobuild), and stuff all the notebooks in /doc instead of in /examples. This is what Param does, although Param doesn't build JupyterLite so there may be other things to adapt.

It doesn't mean nbsites is no longer a dependency, it should still be one to pull the shared templates and CSS.