3 ms·
If the problem is longevity, then they should just be able to easily export the contents to a format that can easily be archived and then turned back into a wor
by preommr 6y ago
If the problem is longevity, then they should just be able to easily export the contents to a format that can easily be archived and then turned back into a working blog with another platform.
Most blogs are as simple as markdown files, with maybe some complexity in referring to other media files like images, and a key/value map in the form of front matter. That's not very difficult to serialize.
- glaberficken 6y agoRegarding longevity. Here is a nice setup that should last well until after you are dead: Write your articles as plain .txt when you don't need images. Or as handwritten html when you do (use relative links and dump the images into a subfolder) You can simply have pre-made templates for this that you copy and paste manually. Create an account at archive.org Upload your writings root folder. As suggested here: https://news.ycombinator.com/item?id=23650600 https://news.ycombinator.com/item?id=23650600 your writings can live on in a url like https://archive.org/download/test_blog_2020/test/blog/ https://archive.org/download/test_blog_2020/test/blog/ You can even add custom metadata so that it is searchable in some future incarnation of archive.org (doubt they will ever break the existing metadata even if at some decades down the line someone decides to redesign the whole thing) archive.org is becoming such an important "ark" of knowledge that in theory there will be a very high chance a copy is preserved somewhere for decades to come. (barring some large scale digital societal collapse)
- chubs 6y agoI was thinking about that issue too! My idea was that my app would have an 'export to Hugo' option so at any time you've got that as an 'escape hatch' or upgrade path, so no risk.