3 ms·
The solution is pretty clear to me but to my knowledge it doesn't exist and the economics of creating it are not that favorable. You need to have a free github
by ben_jones 8y ago
The solution is pretty clear to me but to my knowledge it doesn't exist and the economics of creating it are not that favorable.
You need to have a free github/publisher side cache which mirrors the public github repository of the code example. The example should be rendered server side without a javascript library for syntax highlighting / formatting. This way the author, or more likely a reader because the author abandoned the post a second after writing it, can make progressive updates and deprecations - sort of like stackoverflow where an answer can live on past the life of its author.
This is not a rife target for a start-up and most likely would have to be offered by a larger player. The service needs to be long-lived and reliable from an operational perspective and its pricing model is not clear as most developers would not pay a dime for it. Github is the most favorable target, I'd pay an extra couple dollars a month to "upgrade" my github account for this functionality. Github Gists are already pretty close to what we need but miss out on a few key features for use in independent blogs (presumably a rate limit and a limited scope that may be too narrow for an example, it might need a full repository).
- tedmiston 8y agoI think you could achieve the "runnable blog post" component via a site like Glitch. http://about-glitch.glitch.me/about/features/ http://about-glitch.glitch.me/about/features/ https://medium.com/glitch/what-is-glitch-90cd75e40277 https://medium.com/glitch/what-is-glitch-90cd75e40277 Not sure if it is possible to hook it up to a CI or Git hook.