How It Works

To work its magic, Quire packages together a number of programs, which play a critical role in the long-term discoverability, longevity, and multiformat output capabilities of Quire publications.

  • Apple’s Xcode is a set of developer tools for your Mac. (Does not apply to Windows users.)

  • Node.js enables you to run JavaScript on your computer.

  • PrinceXML is used to generate PDF/print versions of your publication.

  • Pandoc is used to generate EPUBs and MOBIs.

  • Kindle Previewer is used to generate the MOBI.

  • Hugo is the that creates the online version of your publication. The file structure, layout templates, partials, and shortcodes of Quire are all Hugo conventions structured to allow for more formal digital publications. In other words, you can use static site generation to create dynamic websites incorporating traditional print publishing conventions, like tables of contents, copyright and authorship information, linear reading orders, etc. Visit the Hugo Documentation for more information.

Static Site Generation

At the heart of Quire is static site generation. A like Hugo, the one under the hood in Quire, allows users to keep content in plain text with very simple, human-readable markup. Rather than relying on ongoing build processes through a server that needs to be continually maintained, static site generation keeps the complexity of building the site at the point of publication. Unlike websites with short lifespans, even if certain technology becomes obsolete, Quire files will continue to be accessible. The static site generator also enables the conversion of plain text content into formats other than online sites, including PDF, e-book, and even print. Continue reading if you’re curious to know how it works!

While [Quire] publications take advantage of the latest technology, the fact that they are built from plain-text files and as open-source static sites helps to ensure they will never be dependent on soon-to-be-out-of-date platforms and are much more likely to be compatible with the technologies of the future.

—Ruth Evans Lane, Getty Publications Editor

What Is Static Site Generation?

In traditional website publishing, a content management system (CMS) is connected to collections and image databases (1) and set up on a server (2). The CMS is used to create the website, and once the website is published, the CMS rebuilds the site pages each time they are loaded by a user (3). Thus, the CMS must be kept running for the lifetime of the publication.

In traditional website publishing, a content management system (CMS) is connected to collections and image databases and set up on a server.

In static site publishing, the CMS is just software, and a folder of files on your computer (1) used to build the site. The site files are then uploaded to the server (2), where users can access them directly (3). You only need to run the site software and upload new files if you want to update the publication.

In static-site publishing, the CMS is just software and a folder of files on your, the publisher’s, computer that are used to build the site.

And yet, despite the name, static sites can be as dynamic and interactive as you want them to be, thanks to the full support of the complete web platform (HTML5, CSS3, and JavaScript). Zoomable images, interactive maps, and embedded video and audio clips are just a few of the features that can be included.

Additional Resources on Static Site Generation

The following resources were created by Quire community member, Chris Diaz (@chrisdaaz), for a website he developed as a teaching tool for librarians interested in static site generators as digital publishing tools.

Static Web Publishing for Digital Scholarship: Lesson Plan
Introduction to Static Site Generators

See It in Action

A six-minute introduction to working in a static site generator like the one that powers Quire.