Static Web

Static websites are a collection of HTML, CSS, JS, images, and other files that are delivered to users exactly as they are on the server.

You can think of a static website as a shared folder of readonly files exposed on the web. The URL in your web browser is just a path to find a document in a folder, generally representing a request for an HTML file in a specific location on the server.

In the olden days static web was the norm, but database driven dynamic web sites have dominated the last decade. Dynamic websites use a server-side programming language to create pages on the fly when a user makes a request. Thus a URL represents a query to the application, rather than an existing document on the server. Think of complex sites such as social media, where users are constantly adding more data and there is no “static” documents, but streams of ever changing content.

In dynamic platforms content, templates, and metadata are usually stored in a database. For example, the popular content management systems WordPress and Drupal use the scripting language PHP and database MySQL which must be installed on the server along with the CMS application. For each page that a user visits, the server processes the request on the fly, pulls info out of the database, puts it together with template parts, and delivers the final results back to the user. This enables complex interactivity such as comments, customized views, user management, and a web-based admin interface.

This is kind of magical, but does come with costs. For quality performance you need beefy servers to support both your user side and admin workflows. An increase in traffic can over tax server processing, requiring more CPU or more servers to scale. These are heavy, complicated pieces of infrastructure–they use a lot of energy, they require system admin support, and need constant updates and maintenance to avoid major security risks. Setting up a platform such as Drupal or Omeka isn’t just set it and forget it! You are adopting a puppy that needs constant ongoing attention and care.

Deployed static sites are much less needy–think of it as the contrast between keeping a folder of files vs maintaining software. Static sites can provide high performance and scale with minimal server resources. Without updates your site may start to look dated, but will keep working and won’t create security risks. The ongoing costs are minimal (if not free). Rather than keeping up with your system admin work, you can go build something new!

Thus, despite the power of dynamic sites, static web has experienced a boom since around 2015 in the web development landscape. Driven by static website generators and Jamstack methods, the modern static web approach has become a viable alternative because it offers some advantages over heavy dynamic infrastructure:

contributor: Evan Peter Williamson (University of Idaho Library)
last update: 2021-08-04