3 ms·
I have been on this whole journey of plain-text, longevity, legacy, and similar ideas. I recently moved my 20+ year old blog[1] to a plain-text (Markdown) and w
by Brajeshwar 5y ago
I have been on this whole journey of plain-text, longevity, legacy, and similar ideas. I recently moved my 20+ year old blog[1] to a plain-text (Markdown) and will continue to make it simpler that it should continue to last as long as it can be served out of the simplest hosting possible.
HTML in its raw form is very hard to read. I wanted something simple enough but still has some formatting[2] -- Markdown did that while I avoid spicing it up with formatting.
Right now, it is on Github and if needed, my 13-year old can edit directly there and it will update my website.
I hope that in few years, I shouldn't have to rely on Github either but, hopefully, decentralized that it is somewhere/everywhere on the Internet that it will live it as long as my domain is renewed.
1. https://brajeshwar.com/2021/brajeshwar.com-2021/ https://brajeshwar.com/2021/brajeshwar.com-2021/
2. https://github.com/brajeshwar/brajeshwar.github.io https://github.com/brajeshwar/brajeshwar.github.io
- lmm 5y agoI agree with the original markdown git repo being what's important. I treat the whole web stack as an implementation detail for rendering the markdown I wrote, so I've set my blog up as just serving a minimal header and footer to render that markdown as a web page (using strapdown.js), so that it's still fairly readable in raw HTML form and you can read it with telnet in a pinch. IMO that's a lot more valuable than worrying about progressive enhancement or no-script functionality when your page still requires a hugely complex CSS/HTML engine to render it.
- Brajeshwar 5y agoCool. Looking at Strapdown.js - https://strapdownjs.com https://strapdownjs.com