Presentation Open Access

The Prefabricated Website: Who needs a server anyway?

Martin Holmes; Joseph Takeda

Citation Style Language JSON Export

  "publisher": "Zenodo", 
  "DOI": "10.5281/zenodo.3449197", 
  "author": [
      "family": "Martin Holmes"
      "family": "Joseph Takeda"
  "issued": {
    "date-parts": [
  "abstract": "<p><em><a href=\"\">Project Endings</a></em>, a collaboration between digital humanists and librarians, is devising principles (<a href=\"\"></a>) for building DH projects in ways that ensure that they remain viable, functional, and archivable into the distant future. Endings principles cover five components of project design:</p>\n\n<ul>\n\t<li>\n\t<p>Data</p>\n\t</li>\n\t<li>\n\t<p>Products</p>\n\t</li>\n\t<li>\n\t<p>Processing</p>\n\t</li>\n\t<li>\n\t<p>Documentation</p>\n\t</li>\n\t<li>\n\t<p>Release Management</p>\n\t</li>\n</ul>\n\n<p>Previous <em>Endings</em> work has focused on Data and Products (Holmes 2017; Arneil &amp; Holmes 2017) and diagnostic tools for monitoring project progress (Holmes &amp; Takeda 2018 and 2019). This presentation will deal with the mechanics of Processing, focusing in particular on building large static sites which are resilient because they have no requirement for server-side technology at all. We will use the <em><a href=\"\">Map of Early Modern London</a></em> (MoEML) project as a case study.</p>", 
  "title": "The Prefabricated Website: Who needs a server anyway?", 
  "type": "speech", 
  "id": "3449197"
All versions This version
Views 143143
Downloads 118118
Data volume 177.8 MB177.8 MB
Unique views 127127
Unique downloads 106106


Cite as