jupyterlab-workshop
Guided, interactive workshops inside JupyterLab.
Teaching in JupyterLab usually means a notebook with explanation between the code cells. Learners read down it pressing Run, everything has to be a cell in one language, and nothing can tell whether a step was done. This extension separates the instructions from the work: they live in a side panel, one page at a time, and each step is a clickable action that does something real in the JupyterLab session beside it, in a terminal, the editor, a notebook, a kernel or the interface itself. Workshops can check what the learner has done, ask questions, collect values, hold pages until requirements are met, and snapshot the working directory, and the subject can be anything JupyterLab can host, including JupyterLab itself.
A workshop is a directory with a workshop.yaml manifest and Markdown
pages. The format is text based and git friendly. A workshop runs
wherever JupyterLab runs, and can be handed to learners through a
published collection, a Binder link, a container image, or a static
JupyterLite site that runs entirely in the browser.
Install
The package is a prebuilt JupyterLab 4 extension with its server
extension, installed into a virtual environment alongside JupyterLab
with uv add jupyterlab jupyterlab-workshop or the pip equivalent, or,
to run workshops without a project of your own, as a tool with
uv tool install "jupyterlab-workshop[lab]" and then
jupyter-workshop launch --root ~/training --collection <url>.
Getting started
walks through the setup, runs an example workshop and scaffolds one of
your own; the jupyter workshop command that comes with the package
lints, self-tests and publishes workshops, and author mode in JupyterLab
edits them in place.
Learn more
-
Launch the showcase on Binder: three short workshops that show what the extension does and why, in a full JupyterLab with a real terminal, from the showcase repository that is also the pattern for publishing a collection of your own. Or try the demo: the Hello JupyterLab example running in JupyterLite, started afresh on every visit.
-
How workshops work and the tutorial, which writes a small workshop from nothing and publishes it.
-
Using workshops for learners and Deploying workshops for Binder, containers, JupyterHub and locked-down images.
-
The documentation for the rest: every action a page can use, checks and forms, variables, layouts, platforms, JupyterLite, publishing, trust, the manifest and settings references, the command line and authoring in JupyterLab.
-
Source, issues and contributing: see
CONTRIBUTING.mdin the repository for the development setup.
Developed with AI
This package was developed with the help of AI coding assistants, working to the author's design and direction, with the author reviewing what they produce. If you would rather not use software produced that way, that is understood, and this package is not for you.
License
Apache License 2.0.
1 maintainer
Metadata
1 maintainer
Release files for jupyterlab-workshop 0.22.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| jupyterlab_workshop-0.22.1.tar.gz | 1.5 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jupyterlab_workshop-0.22.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 MB
Release files / jupyterlab_workshop-0.22.1.tar.gz
| Download URL | jupyterlab_workshop-0.22.1.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d80c009b869eb369a1cb7957334807db4a5a6f72ea89c3f12f68acdb3bbd1cba
|
|
BLAKE2b-256 checksum How to use checksums |
4ff5a57357632703a6ecafa2e9debd57f090122f2821cf191bd6acadd53abeb2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency logRelease files / jupyterlab_workshop-0.22.1-py3-none-any.whl
| Download URL | jupyterlab_workshop-0.22.1-py3-none-any.whl |
|---|---|
| Size | 564.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
769e61fa8fe750d8d2e8aae7ce1bac6013b1ae8863bad296c074d2df7e82d3ab
|
|
BLAKE2b-256 checksum How to use checksums |
d35f3c3ef9cd75c1a8708c2dd62b39556ccaa469c3e20df538cf9a552381a3cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency logSecurity for jupyterlab-workshop 0.22.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for jupyterlab_workshop-0.22.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
