To claim your project's products are Endings-compliant is to promise that they adhere to the Endings principles. This means that:

  • All code (XML, CSS, HTML, etc.) has been thoroughly validated.
  • All internal links have been tested and targets confirmed to exist.
  • All internal links are relative, so the site can be hosted anywhere.
  • No server-side scripting (PHP, JSP, Python etc.) support is required.
  • No backend database software is required.
  • Every page on the site carries the same clear edition and date information, so that it can be cited effectively.
  • There are no external dependencies; or if there are, then they are peripheral to the main functionality, and when they fail, the results will not be significant.

You can download a package of our logos in various formats, and add one to your site, linking to this page.

We have developed the Endings principles based on the results of a five-year research project on the sustainability of digital humanities projects. In order to give your project's website the best possible chance of survival; and to make it as easy as possible for a library, archive, community organization, or other memory institution to assume ownership of the site for long-term preservation and/or access; you should have a final state of your website in mind as you begin your project (although it is never too late to start this process). For the purposes of your research, collaboration, or work, a dynamic website might make perfect sense during the duration of your project. But, you should plan adequate resources (time and funding) to staticize your site as well as to find a final long-term home for that site (in a library, archive, etc.).