Skip to content
This repository has been archived by the owner on Sep 30, 2022. It is now read-only.

Importing an Observable notebook into a standalone application

License

Notifications You must be signed in to change notification settings

severo/observable-to-standalone

Repository files navigation

Observable notebook to standalone application

Various methods to migrate an Observable notebook to a standalone webpage.

Example notebook

The joyplot notebook is used as an example throughout this repository.

Screenshot of a joyplot notebook

Examine the results of the migration to a standalone application:

Using ObservableHQ runtime

An Observable notebook can be run as a standalone application using the @observable/runtime library, outside of the Observable platform.

The recommended method is to bundle all the modules into a single JavaScript file: "Bundle" method

Diagram for the "Bundle" method

See it in action by Philippe Rivière on the Spherical contours notebook:

Two simpler methods are possible. The first one is to download and extract tgz from Observable notebook to use the default index.html file provided in the tgz file: "Default Observable export" method

Diagram for the "Default Observable export" method

The second simpler method is to get JavaScript modules from api.observablehq.com at runtime: "Request Observable API" method

Diagram for the "Request Observable API" method

Independent of ObservableHQ runtime

A totally different approach to migrate an Observable notebook to a standalone application is to rewrite the code from scratch: "Rewrite from scratch" method

Diagram for the "Rewrite from scratch" method

References

Credits

Project developed for the LIRIS M2i project by Sylvain Lesage with the help of Philippe Rivière, Romain Vuillemot and Mike Bostock.

About

Importing an Observable notebook into a standalone application

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published