How to Choose a Static Site Generator
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
A static website is made of pre-built pages with content that doesn’t change between user visits. Because each page is delivered to the browser the same way every time, static pages are often much faster than pages with dynamic content that rely on the server to process each request for each page load.
A static site generator is an application that converts files (usually stored locally) into webpages. This allows content creators to focus on content, without needing to learn code or stylesheets, and without needing to manage many of the complexities of a backend server.
Content Management Systems (CMS) make it easy to create and manage content through an interactive front-end. They rely on the server to retrieve data from a database with each visit. This allows pages to show dynamic content, but slows the delivery to the end-user, since each page is built as it’s requested. Because each page request is sent to the server, and because some major CMS features rely on plugins, system security may be compromised if precautions aren’t taken.
A static site generator lets you create content offline in a text editor and preview what the final web page will look like before it is published. When it’s time to build the pages, a short command compiles all new and changed pages within seconds.
While a static site generator doesn’t need a complex backend and database, it does generally require that the compiled files be moved to a server. This step can be automated, but might require using the command line to set up.
Many static site generators have pre-built themes for easy blogging. This allows bloggers to write in a distraction-free environment, while still having the option to format text using Markdown.
Static sites can also be used for documentation. For example, Linode’s documentation library is built using Hugo. Check out the source Markdown file for this guide on GitHub to see what it looks like before Hugo applies our custom theme.
Personal or event websites (portfolios, wedding sites, and campaign pages) are also easy to set up using a static site generator.
StaticGen has an updated list of static site generators. To find the right one for you, consider the following:
- Tools you build with - Node / Ruby / Python / Git / Markdown / etc.
- Themes - have you found a theme you’ve fallen in love with?
- Plugins - will you be able to connect it to that thing you need?
- Language - is the generator available in your language?
- Project activity - is the generator still in active development?
Since static site generators are easy to set up, it’s worth installing a few and creating test pages to see which works best for your workflow.
- Jekyll: Touts itself as “blog aware,” meaning it was made to make blogging easy. Jekyll was built by GitHub and is consistently one of the most popular static site generators. The larger community means a great library of available themes, plugins, and available answers. GitHub pages can be configured to automatically build and host a GitHub repository using Jekyll. Jekyll installs via RubyGems and uses Liquid for templating.
- Hugo: Builds pages quickly. Hugo has a built-in LiveReload, so you can see your changes in a browser as soon as changes to a tracked file are saved. Hugo is written in Go and uses Go templating. It also uses shortcodes to easily extend the types of content that can be included in a page. Hugo can be installed through a package manager or by downloading a binary.
- Hexo: Focuses on speed and simplicity, and is still flexible enough to use both Jekyll and Octopress plugins. One command can deploy a site to your Linode using Dokku or SFTP. Hexo uses Node.js under the hood, and can be installed with NPM.
- GitBook: Built around Git, GitBook aims to make many of the features that make Git useful (branches, pull requests, version tracking) accessible to users more familiar with traditional desktop publishing. GitBook is commonly used for technical/API documentation, user manuals, or knowledge bases, and has built-in templates for these and other types of content.
- Choose a static site generator and follow the installation instructions on its site.
- Install a theme with features that most closely resemble your needs. Remember that you can customize almost any aspect.
- Edit and save a few sample pages in a text editor like Atom, Sublime, or Neovim.
- Note that each generator requires different meta information. Refer to the official documentation to learn more about available features.
- Preview your pages if available.
- Instruct your static site generator to build the site.
- Move the newly built or updated pages to your web server.
To make static site content management even easier, check out HeadlessCMS for a selection of CMS systems for your static site generator. A front-end serves as an intermediary between your content and the site. It allows you to create and edit in a familiar and easy to use environment, and then automates the command line functions.
While convenient, using a front-end gives up some control and adds more moving parts (and potential points of failure) to what should be a simple system.
A static site doesn’t have to mean a read-only user experience. There are limits to what a static site can incorporate, and if your site relies heavily on user interaction you may want to consider a different solution. However, most of the interactive features commonly used in blogs and personal websites can be easily included through the use of third-party extensions.
You can add:
This page was originally published on