Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Considerations for new infrastructure #109

Open
dopplershift opened this issue Aug 10, 2020 · 0 comments
Open

Considerations for new infrastructure #109

dopplershift opened this issue Aug 10, 2020 · 0 comments

Comments

@dopplershift
Copy link
Member

We've been kicking around continued rearchitecting this, so I just wanted to capture some thoughts (and close some browser tabs). The problem with the current stack, Nikola, is that it doesn't seem to buy us much while requiring a whole new set of effort to theme it up consistent with Unidata stuff. Other options:

  • Jupyter Book: Works well with notebooks and markdown. Still have our theming issues. Also does not seem to have a gallery
  • Sphinx with notebook extensions: Still theming, but at least a common stack to the rest of the Python projects.
  • nbconvert + jekyll: Can re-use the jekyll work that's been done for e.g. netCDF-java. Downside is we'd have to continue doing all the notebook stuff on our own.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant