Just like vinyl LPs, static sites are making a comeback, evidenced by the wide array of static-site generators now available. This practical book shows you hands-on how to build these simple sites for blogs and other use cases, and how to make them more powerful. In the process, you'll work with some of today's more mature and popular static-site generators.
Authors Raymond Camden and Brian Rinaldi explain the advantages of using static-site generators for building fast and secure sites. Web and frontend designers and developers will also explore methods for adding dynamic elements and for migrating an existing CMS to a static site.
Build a basic four-page static site with the Harp generator Create a simple blog with Jekyll Develop a documentation site with Hugo by generating site files and creating the layout Add dynamic elements, such as forms, comments, and search Integrate a CMS with tools such as CloudCannon and Netlify CMS Use one of several options to deploy your static files Learn methods for moving an existing CMS to a static site
An interesting book that gives an overview of static site generators and what they can do to help you create websites without using dynamic site generators.
The book starts with a brief overview of how static site generators work and the advantages and disadvantages of using such site generators. A simple website is then created using Harp, showing how templates, partials and data are put together to generate the website. A blogging site is then created using Jekyll, showing how blog posts can be put up and organised. A documentation site for a sample programming language is put together using Hugo showing how to categorise the information.
Adding dynamic elements to static websites are then provided, like handing forms, comments and custom search are then covered. Finally, options for using a CMS (Content Management System) to generate the information for static site generations are mentioned for those who are used to such system for content entry.
Methods to deploy a static site are then covered, mainly cloud servers, ending with how to migrate your current dynamic site to a static site.
In summary, the book is a quick introduction to static sites and may give your some ideas on how to use one and what to look for in a static site generator.
The book might be cute, but it fails as the author has a very poor grasp of the concepts used. Sure, he might be a wizard and make you a canned static site in 20 minutes, yet the rest is pretty much crap.
> Static sites are fast.
Actually they are fastER than their dynamic counterparts because there is less computing power involved. A "fast" static site on an overload server or over a poor connection will still timeout or simply display later than a Gmail page with all bells and whistles on.
> Static sites are secure.
Here is a big problem stemming from the shallow understanding of the technology. The "site" is just some text and media files. There is a server doing all the serving. In the case of a static site, there can be only a HTTP server. Of course, there can be a lot more servers along the way, but the only requirement is the HTTP server. Now, a more complex service, like Gmail involves the HTTP server, but also an email server, some database servers, some extensions for the language used to program the extra functionality, and a lot more servers simply mean a lot more failure points.
Overall the book is a waste of paper. Just Google "static html site generator" and you will find lists of such software. Pick one and the more poor documented ones will have as much information as this book has. Some of the more helpful ones, say Jekyll and Hugo, both mentioned in this book, are far more useful in their official documentation. Add the many fan sites and forums and this badly written book also becomes a waste of your time, not only of trees.
Not a bad intro to static sites, but I was expecting more depth from a book (as opposed to a series of blog posts).
Good mention of Lektor (https://www.getlektor.com/), but otherwise pretty basic and does not draw a good line (from the architectural point of view), when not to go static: last chapters talk about deployment options, form and comment providers, but many people will be just fine having all those on a dynamic site that will cost them less to maintain (unless they might get huge visitor spike, but this is me talking about those architectural tradeoffs now).
I am also a bit disappointed in general about the format books in the 21st century take: short, rather shallow and covering the tech that will become irrelevant in less than a decade.
This was an interesting book, because I have always hand coded my sites using straight html and php code. I don't use generators of any kind. Indeed, I wasn't even aware that static page generators existed (well, back in the 90s, I was aware of frontpage, but that program was one of the worst generators I've ever had the misfortune of arguing with it's output), so I've always just hand coded my html code, adding php when it was necessary to have dynamic content. This book offers a view into how it's possible to maintain a static site using tools that will allow you to treat your site like a modern day CMS (such as Drupal or wordpress). It's a very interesting read if you're a webmaster that likes to maintain their own pages without the benefit or hassle of cms systems.
It’s ok for an introduction of what working with Static Sites is and what options are out there. Nothing more.
Once you have chosen one tool (Hugo, Jekyll or Gatsby that BTW is not considered been now one of the leaders), this book is short in resources. You will find faster how to do anything you need just googling than reading this book. A bit disappointing.
A great run through of the big players in static site frameworks in several languages. More details than I wanted to know, and the book is better for it. Nicely done!
Good intro to all the possibilities with static site generators. A little dated by now with some dead links. Use it as a primer then choose one and dive in.