stevejpurves
Joined 12 years ago
Joined 12 years ago
I've been working on some integrations along the lines of explorable texts that are backend by compute in jupyter - like this mini one on fourier series https://curvenote.github.io/demo-fourier/ (pres the power button to connect to a binder instance).
There ia notebook behind the scenes, and the idea is to try and move from custom web/js development towards something that a content creator say who is familar with python can use. Also open up the possibility of computing with libraries in the python ecosystem, and with compute needs beyond what we can achieve in the browser.
Still this example is a one off react site, built with JS knowledge.
Working from the other direction I'm also working with folks on a static site generator that can use Markdown(MyST) and Juptyer Notebooks to build book like content, this is a little like JupyterBook but with a JS stack that can integrate the explorable JS based interactivity on the link above.
The idea is again to let people focus on content and have a site generator let them build the deployable book. The cli that does that is open source and in beta at the moment in terms of readiness https://curvenote.com/docs/web but we're excited about what it can do already and busy working on the explorable integrations - looking for feedback and direction too :)
some example of building with it:
- my blog https://www.stevejpurves.com/la-palma-earthquakes - a book like report https://climasoma.curve.space/
Your other comment about picking the horizon of interest is really on point, that's where automated interpretation as it's been buzzworded to hell to date as had had no chance and has never lived up to how it was pitched. Many tools just made the problem worse.
That fact that this might change in some distant future, well it may be solved in some capacity but is it really worth the effort? Given that exploration has a limited future.
We are introducing templates for sure. Word is on our roadmap but first up is to introduce LaTeX templates including user defined ones. We started mapping out the initial UI and we've got some ideas for how to allow public and community generated templates to be added to the system too, we went through these in a recent meetup, it's recorded so you can see more here => https://youtu.be/r46wN4KWPac?t=1024
When you look at work like this, and also the work produced by distill.pub achieving it is beyond the reach of most researchers. Right now that means someone would need to custom build the experience -- html/web development skills required. One of our aims with Curvenote is to bring that within the reach of most researchers, making it easy to publish interactive content by default.
Documents can then be exported as a PDF which uses Latex for typesetting, currently that's with a default template, but we're working on user defined templates right now.
When people's workflow is not data heavy, we think there are other features making Curvenote an attractive place to work; the WYSIWYG style of writing, real-time comments and easy sharing on one hand but also how Curvenote helps you easily reuse, update and build on your existing content.