Software Request: Open Source Personal Content Repository

Posted by Paul Korm
Sep 11, 2018 at 10:42 AM

Jan S’s suggestion of org mode is a good example of future proofing—because it has a long history of having been future proof. It endures.

The key to future proofing your data store is to

1) Make sure your document types are likely to endure and are not proprietary or custom formats. For example, if you understand JSON and do not understand how to transform JSON (or XML) files then do not use apps that create these files. Markdown is often cited as “future proof”
2) Don’t store your content solely online in a cloud—behave and plan as though there is a 100% chance of failure of any given online repository in the course of your career.
3) If you store offline, then refresh your storage media at least once every 24 months. There is also a 100% chance of failure of every storage device.

Wikis are not designed for effective document storage. Your file system is.

Remember the rule 3-2-1 rule: store every document 3 times, in at least 2 locations, 1 of which is off site.