Hi, We are combining Markdeep and STON in a light format to share and publish Pharo powered data stories and visualizations written/crafted in Glamorous Toolkit's Lepiter. In this link you can find a demo of the published output, that, of course can be imported back to Lepiter: https://mutabit.com/repos.fossil/malleable-systems/doc/trunk/wiki/en/malleable-systems-wiki--23fm1.md.html And below you can find a preview of this data story. Our light format have some differential values over other popular data stories publishing formats, like Jupyter Notebook: a) Its human and browser readable, in contrast IPynb JSON and Python exports are readable by one, but not the other. b) it only requires (3mb) Fossil + (350K) Markdeep to be stored, versioned, shared and published. Other DVCS, web folders can be used and is a big contrast with complicated and/or oligopolistic support to make a format (Ipynb) web renderable. c) The same published document can be imported back to Lepiter. When a Jupyter document is published as HTML, it can not be imported back from there to Jupyter (I imagine something similar happens with RStudio or OrgMode, but I have not experienced data workflows on the last tools by myself). And here is the respective Nitter/Twitter thread with details and alternative narrative: https://nitter.net/offrayLC/status/1490130769603444742#m <https://nitter.net/offrayLC/status/1490130769603444742#m> Cheers, Offray https://i.imgur.com/GhbaSZc.png

Hi again, Something happen with the foreground/background colors. So here it comes again. ================ Hi, We are combining Markdeep and STON in a light format to share and publish Pharo powered data stories and visualizations written/crafted in Glamorous Toolkit's Lepiter. In this link you can find a demo of the published output, that, of course can be imported back to Lepiter: https://mutabit.com/repos.fossil/malleable-systems/doc/trunk/wiki/en/malleable-systems-wiki--23fm1.md.html And below you can find a preview of this data story. Our light format have some differential values over other popular data stories publishing formats, like Jupyter Notebook: a) Its human and browser readable, in contrast IPynb JSON and Python exports are readable by one, but not the other. b) it only requires (3mb) Fossil + (350K) Markdeep to be stored, versioned, shared and published. Other DVCS, web folders can be used and is a big contrast with complicated and/or oligopolistic support to make a format (Ipynb) web renderable. c) The same published document can be imported back to Lepiter. When a Jupyter document is published as HTML, it can not be imported back from there to Jupyter (I imagine something similar happens with RStudio or OrgMode, but I have not experienced data workflows on the last tools by myself). And here is the respective Nitter/Twitter thread with details and alternative narrative: https://nitter.net/offrayLC/status/1490130769603444742#m <https://nitter.net/offrayLC/status/1490130769603444742#m> Cheers, Offray https://i.imgur.com/GhbaSZc.png On 8/02/22 16:19, Offray Vladimir Luna Cárdenas wrote: > > Hi, > > We are combining Markdeep and STON in a light format to share and > publish Pharo powered data stories and visualizations written/crafted > in Glamorous Toolkit's Lepiter. In this link you can find a demo of > the published output, that, of course can be imported back to Lepiter: > > https://mutabit.com/repos.fossil/malleable-systems/doc/trunk/wiki/en/malleable-systems-wiki--23fm1.md.html > > And below you can find a preview of this data story. > > Our light format have some differential values over other popular data > stories publishing formats, like Jupyter Notebook: > > a) Its human and browser readable, in contrast IPynb JSON and Python > exports are readable by one, but not the other. b) it only requires > (3mb) Fossil + (350K) Markdeep to be stored, versioned, shared and > published. Other DVCS, web folders can be used and is a big contrast > with complicated and/or oligopolistic support to make a format (Ipynb) > web renderable. c) The same published document can be imported back to > Lepiter. When a Jupyter document is published as HTML, it can not be > imported back from there to Jupyter (I imagine something similar > happens with RStudio or OrgMode, but I have not experienced data > workflows on the last tools by myself). > > And here is the respective Nitter/Twitter thread with details and > alternative narrative: > https://nitter.net/offrayLC/status/1490130769603444742#m > <https://nitter.net/offrayLC/status/1490130769603444742#m> > > Cheers, > > Offray > > https://i.imgur.com/GhbaSZc.png >