Problem

When I start JupyterLite, it shows the default UI with the Launcher and File tree, which is good! When I get a few documents and/or linked outputs open, and restart JupyterLite, I lose the state of what I was working on.

Proposed Solution

Support an implementation of api/workspaces/, as described in the jupyterlab_server API spec.

The first time out, starting from the default, the workspace can be saved either to the same localForage (as they reference contents paths), or to a separate one altogether, and introduce (further) router hacks for ?workspace=<name-of-workspace> (and ?reset, probably).

When reloading, this would be consulted. This is might be sufficient for an MVP, but would probably still be broken.

Supporting the import/export of *.jupyterlab-workspaces files (and being able to pre-populate/pre-index this folder) would make it much easier to drive/link to a very specific lab configuration e.g.

• for a docs site:
  • https://my-docs.rtfd.io/lite/?workspace=docs
    • https://my-docs.rtfd.io/lite/?workspace=dashboard
• for a particular snippet in a blog post
  • https://my-blog.engineering/lite/?workspace=example-1-layout

Additional context

• might help Embedding jupyterlite into a static site #131
• might need Support federated serverlite extensions #104, but this should probably be first-party