6 ms·
Blog-cells: Interactive code cells for static sites
- kolme 3y agoThis looks great, if anything I think it's a shame it's not implemented using Web-Components, as they would be a perfect fit here for several reasons: intuitive, ease of use and maybe would even solve some security concerns.
- sesm 3y agoHow would you allow cells to communicate with each other while being isolated from the rest of the page?
- microflash 3y agoThrough events. You can add reactivity and state propagation through events.
- tommiegannert 3y agoWhat are your security concerns?
- kolme 3y agoCode in the cells breaking out and manipulating the page where they are embedded.
- tlarkworthy 3y agodon't upload malicious code in your blog then. The same thing happens when you import a 3rd party library. I see this as a feature not a bug.
- gitgud 3y agoPretty sure adding a JS interpreter in your webpage is impossible to do without security concerns... But maybe using an <iframe> would make it a little more secure...
- seanwilson 3y agoWhat's the worst that could happen with an `<iframe sandbox="allow-scripts">` on your page (where the iframe will be treated as if it's from a different origin to the current page)? https://codepen.io/ https://codepen.io/ runs custom user JavaScript, HTML and CSS for example via iframes.
- cxr 3y agoLike CSP, iframes' sandbox attribute was conceived for an environment where it only works as part of a defense-in-depth strategy. It had to be; iframe is not a completely new element—consider what things looked like the day after the first browser to support the sandbox attribute was released: you had some X% of users who would be protected by it, and some Y% who would not, where Y >> X, and the set of people belonging to Y weren't "wrong" for belonging to that set—an author expecting sandbox to be the first, last, and only line of defense against malicious code is the one in the wrong. (Same with CSP.)
- seanwilson 3y agoLooks like `iframe sandbox` has been supported in major browsers for around 10 years though, including IE10.
- cxr 3y agoThat doesn't change the fundamental character of sandbox being one part of a defense-in-depth strategy instead of being the first-last-and-only line of defense. When you begin using and relying on a security-related feature in a way it was never designed to be used, then you are playing with fire and arguably already compromised. Browser vendors can change their implementation at any time on the basis that newer releases still satisfy the intent. Example: what approach are you using in your hypothetical to actually get the cell contents into the iframe?
- xg15 3y agoAs long as a user can only run the code they (or the page author) has entered by themself, I don't see an issue. It gets more problematic if you allow users to store modified cells and link to them. Then a malicious user could write a cell amd trick another user into executing it.
- deleted 3y ago[deleted]
- benno128 3y agoI have a project that does this: https://runno.dev https://runno.dev No shared state between elements, but it’s an interesting idea. Edit: It runs other languages as well, like Python, C, Ruby.
- ldelossa 3y agoWow this is cool. I've been looking for 'runnable C examples' on my blog. Do you know if I can integrate this with Hugo easily?
- benno128 3y agoThanks! If you’ve got a way to add node packages to your frontend then it is pretty straightforward. If not, using unpkg (https://unpkg.com/ https://unpkg.com/) in a script tag should work. Happy to help you figure it out! Post in the discussion board on GitHub or email me (address on the website).
- tlarkworthy 3y agoOh this would be such a good fit for my dream of serving federated backend code from web readable hosting https://webcode.run/ https://webcode.run/
- jraph 3y agoI could not see any cell because I have JS disabled by default. blog-cells's readme addresses this: > Using pre tags instead of script tags > Script tags are great for defining notebook cells since they can hold pretty much any code without escaping. However, they are invisible by default, meaning that readers won't see anything until blog-cells loads. You can get around this by using <pre class="notebook-cell"> tags instead, however reserved HTML characters should be escaped using HTML entities. <pre class="notebook-cell"> console.log("<b>HELLO</b>"); </pre> I was pleasantly surprised to see this. I know it's a bit less convenient to type because of the entities, but I believe this is the way to go and this should be the main, advertised, method. Progressive enhancement. Keep your content as accessible as possible :-) Now, I do think the result blocks would be better statically rendered if it's going to yield the same result each time they are run. The code runs once, at generation time, and the page is totally readable without JS. It indeed requires a generation step, but I think it's worth it, and blogs usually already have one. I think Emacs has something like this with Org mode.
- scepheo 3y agoThe no-JS problem could also be solved by some CSS instead: script[type="text/notebook-cell"] { display: block; } Which stops you from having to type out all those entities. Once fully supported, you could even put this behind a media query (`@media (scripting: none)`) so you don't have to change the display with JavaScript after load.
- deleted 3y ago[deleted]
- swiftcoder 3y agoIn the context of a static site generator, you'd usually render all those entities with a markdown processor + syntax highlighter anyway.
- bArray 3y agoThis really nice, it has me thinking about running other languages too - very cool!
- spacebuffer 3y agoReminds me of org-babel[0] for org-mode on emacs, it basically does the same thing. it lets you run code inside your org files. [0]: https://orgmode.org/worg/org-contrib/babel/ https://orgmode.org/worg/org-contrib/babel/
- robust-cactus 3y agoThis is awesome, the only thing I'd recommend tweaking is that $ global. I think every post using this would have to explain it to its reader. Two options: 1. Make every exported function a global, or just look like a global. 2. Force users to import and name the blocks I think option 1 for this use case might actually be just fine.
- Vox_Leone 3y agoIt is cool. But doesn't it kind of defeat the whole point of static pages?
- ladberg 3y agoThe point of static sites is to avoid the need for any rendering/compute server-side, which this accomplishes! E.g. you could use this in your GitHub Pages site, which is just served from a CDN without any real backend.
- skybrian 3y agoIs there anything like this for Observable's variation on JavaScript?
- nlunbeck 3y agoReally cool project! The API call functionality could be a good feature for docs, feels cleaner showing the sample response there instead of a dropdown.
- cobertos 3y agoHow does this allow queries against CORS enabled endpoints? I don't see anything special for that. No CORS proxy, no fetch monkey patching, nothing
- deleted 3y ago[deleted]