You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@bsipocz has implemented a very nice continuous integration and rendering into html in the NASA-NAVO/navo-workshop repository. The notebooks are rendered automatically, and CI is run periodically, not just when commits are made. We could adopt the same scheme here.
The text was updated successfully, but these errors were encountered:
Those static pages are beautiful, that's awesome @bsipocz! The main consideration is that the navo workshop uses jupytext to convert between markdown files and Jupyter notebooks. This adds a bit of overhead for contributors and maintainers, and requires users running the workshop locally to do a bit more setup.
navo-workshop did recently convert to using MyST Markdown format. I was not suggesting that we do that here, just yet, but that we could adopt the rest of it. The CI and html-rendering were put in place before the switch to markdown notebooks.
@bsipocz has implemented a very nice continuous integration and rendering into html in the NASA-NAVO/navo-workshop repository. The notebooks are rendered automatically, and CI is run periodically, not just when commits are made. We could adopt the same scheme here.
The text was updated successfully, but these errors were encountered: