What does it mean for a project to be "archive ready"? - projectEndings/Endings GitHub Wiki

We are not alone in identifying the issues around long-term archiving of digital projects; this discussion at Berkeley is typical of many such initiatives. On this page, we will collectively work out what exactly "archive-ready" means for the purposes of Endings:

• functional without a server infrastructure to support it
• dependent only on existing standards with massive support (HTML5, JavaScript, CSS, XML)
• harvestable by archiving tools
• functional when harvested and served up by an archive browser such as the Wayback Machine
• search-engine-friendly (interesting and difficult)
• metadata-rich, preferably in multiple formats