observablehq
Dashboards as consumers of notebook artifacts
Description: Easy export and/or store the contents of a notebook into an Observable artifacts repository.
Why: Notebooks are valuable because they are quick ways to explore data. The user can quickly iterate and filter data through a DTC, create a helper function to create an SVG, and share contents of notebooks with a team member who also has Observable. Notebooks are good for content creation but not necessarily content presentation. Notebooks can provide the building blocks for dashboards and already have permissions baked into a particular view. Artifacts derived from a notebook should have the same permissions as the notebook themselves unless granted otherwise.
Details:
Have a button or some UI in for a single cell that publishes to the Observable artifacts repository. Expose extra scopes as part of the observable login command and a new set of APIs to fetch/download the artifacts. Users of the CLI can call these Observable endpoints within a data loader given that they've authenticated via observable login.
Why Part 2: Notebooks are constantly changing but artifacts are version-controlled. The act of promoting parts of a notebook to an artifact means the user/team is "locking in" the changes and having it be ready for production. We can also think about the possibilities of having a scheduled run with new artifacts posted on a dedicated time interval.
Inspiration:
This is also an easier way to integrate existing users to the dashboard changes and encourage them to work within the "Observable Ecosystem"
closing as not planned; but it's a good idea to simplifying making artifacts from a project (e.g. with playwright).
