Experiment: "Quickstart"-focused README #47
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It took me some digging to understand a few key things I needed for a Jupyterlite "Quickstart," where my use case was basically "put some notebooks on GitHub Pages, or other static site hosting, and have them be shareable and interactive (thanks to Jupyterlite)."
The minimal quickstart steps seem to be:
At that point,
dist/
is a static bundle that can be dropped anywhere, copied into an existing GitHub Pages site dir, etc.The
jupyterlab
dependency was tricky to figure out. It's required for example notebooks to show up on the frontend. Otherwise,jupyter lite build --contents content
will ≈silently fail to outputapi/contents/all.json
(which is required for example notebooks fromcontent/
to be presented to users, cf. jupyterlite/jupyterlite#318 (comment)).Some other thoughts:
deploy.yml
in this repo is a good template for auto-publishing via GHA, which I know is somewhat described in this README, but took me a while to find+appreciate.contents/
, is a powerful "Quickstart" that I didn't glean from my initial skim of relevant repos/docs.how-to-host-your-own-jupyterlite.ipynb
, easily findable in the main demo.Anyway, I appreciate that the README.md in this repo is geared toward beginners; perhaps some of the above (and the README.md I wrote in this PR / my fork) could go in a
quickstart.md
or something?Thoughts welcome, I'm not actually proposing to replace the README wholesale, this is just my take on explaining a quickstart to someone who's already more proficient with Git{,Hub}.