Following yesterday's Clay + #calva demo, here is a Clay + #cider demo with an image processing use case. https://www.youtube.com/watch?v=X_SsjhmG5Ok https://www.youtube.com/watch?v=fd4kjlws6Ts

Thanks, @alex.shulgin. The best overview on that is @timothypratley's part of the London Clojurians https://www.youtube.com/watch?v=skMMvxWjmNM. Clay indeed goes on the same namespace-as-a-notebook path, that other tools such as #oz, Notespace, and #clerk, have taken. We have created Clay to support our current community needs at Scicloj: teaching, documenting, exploring data. Compared to other tools, it is built to • do less, have a minimalistic user interaction • generate static HTML files ◦ so your text is just HTML text, etc. ◦ .. and your pages can be indexed by search engines ◦ .. and your pages tend to load fast • make it simple to send a single value to be displayed • be compatible with the https://scicloj.github.io/kindly/ convention Some of these properties are supported by #oz (and early versions of Notespace). But eventually, we realised that it would be simpler to write a small project from scratch to support the workflow we needed, mostly because we wanted to support Kindly. And that small project is Clay v2. The approach we are encouraging is that anybody should use their favourite tool, but our teaching resources & docs can be written in a way (Kindly) that will work across tools. So we have a draft of a Kindly-Clerk adapter, that will make Clay notes just work in Clerk.