Skip to content
This repository has been archived by the owner on Dec 18, 2023. It is now read-only.

Use bokehjs for documentation #1348

Closed
ndmlny-qs opened this issue Feb 18, 2022 · 3 comments
Closed

Use bokehjs for documentation #1348

ndmlny-qs opened this issue Feb 18, 2022 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@ndmlny-qs
Copy link
Contributor

Issue Description

Investigate using the node package for bokeh in the documentation.

@ndmlny-qs ndmlny-qs added the documentation Improvements or additions to documentation label Feb 18, 2022
@ndmlny-qs ndmlny-qs self-assigned this Feb 18, 2022
@ndmlny-qs
Copy link
Contributor Author

@horizon-blue we discussed attempting to add Bokeh as a node requirement, similarly to how we have plotly installed using our custom component, but Bokeh is not designed as a node module, and cannot be simply added to the project. I'm am working through this in #1406 as I attempt to make the widgets in Jupyter (#1401) display in a Docusaurus build.

I'm in favor of closing this issue, but we could alternatively use Docusaurus's <Head> component to inject the Bokeh JavaScript needed only on the pages we need it, and removing the requirement from being loaded on every page in the Docusaurus config. Let me know what your opinion is on the two options

  1. close and revisit once we know more about getting Bokeh to work in a static react app
  2. update the current Bokeh component to inject the Bokeh scripts from their CDN on pages using the Head component.

@ndmlny-qs
Copy link
Contributor Author

I discovered a way to do this when I started created JavaScript versions of the diagnostics tools.

This was referenced Jun 1, 2022
@ndmlny-qs
Copy link
Contributor Author

closing in favor of creating a single issue for Bokeh plotting and tutorials

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant