mirror of
https://github.com/gohugoio/hugo.git
synced 2024-11-14 20:37:55 -05:00
d2b1030060
0fd7b4169 Fix typo: pygmentsUseClasses -> pygmentsUseClassic 9a3e1c19a Clarify that lower weight gets higher precedence 820d8b581 Clarify the true behavior of hrefTargetBlank #blackfriday eb3aa5e46 Fix typo 9aedb9269 Add examples for removing default taxonomies 772a26f84 Fix source link on maintainance 975c215ae Minor edits. 2bdb1a150 Fix invalid iink 991d2e139 Fix misspelling 60af8dfb0 Update eSolia link d7426b76e Release 0.40.3 4977bd9cf Merge branch 'release-0.40.3' 9946f7108 releaser: Prepare repository for 0.41-DEV beef16b01 releaser: Add release notes to /docs for release of 0.40.3 80c51c55a releaser: Bump versions for release of 0.40.3 21e2934c5 rename `taxonomies.html` to `taxonomy.html` 34a02c289 Add release notes from Hugo 0.7 to 0.15 for completeness b593f512e Update related.md 7c2bf528b Fix the "edit this page" link e8fbc163e Add warning about cond ae15a8831 Add link to Markdown Guide e077dfd65 Added documentation for a new migration tool: BlogMl2Hugo 957bfb6a8 Add Talkayrd, a new commenting system, & fix txtpen link 86acea7f8 Tomango showcase 3c2fc32f1 Fix snap classic command in installing.md 9a76f1737 Merge commit '83bef6955e014d40c0f00db9cebe09113154e999' a4b71fb84 Fix typo git-subtree-dir: docs git-subtree-split: 0fd7b416997bf76cd99e3ae2dfae406cb8b6724a
29 lines
1.7 KiB
Markdown
29 lines
1.7 KiB
Markdown
---
|
|
|
|
title: Tomango
|
|
|
|
date: 2018-05-04
|
|
|
|
description: "Showcase: \"Tomango site relaunch: Building our JAMstack site\""
|
|
|
|
siteURL: https://www.tomango.co.uk
|
|
|
|
siteSource: https://github.com/trys/tomango-2018
|
|
|
|
byline: "[Trys Mudford](http://www.trysmudford.com), Lead Developer, Tomango"
|
|
|
|
---
|
|
|
|
Hugo is our static site generator (SSG) of choice. It's **really quick**. After using it on a number of [client projects](/showcase/hartwell-insurance/), it became clear that our new site _had_ to be built with Hugo.
|
|
|
|
The big benefit of an SSG is how it moves all the heavy lifting to the build time.
|
|
|
|
For example in WordPress, all the category pages are created at runtime, generating a lot of database queries. In Hugo, the paginated category pages are created at build time - so all the computational complexity is done once, and doesn't impact the user at all.
|
|
|
|
Similarly, instead of running a live, or even a heavily cached Instagram feed that checked for new photos on page load, we used IFTTT to flip the feature to work performantly. I've [written about it](https://www.trysmudford.com/blog/making-the-static-dynamic-instagram-importer/) in detail on my blog but in essence: IFTTT sends a webhook to a Netlify Cloud Function every time a photo is uploaded. The function scrapes the photo and commits it to our GitHub repo which triggers a Hugo build on Netlify, deploying the site immediately!
|
|
|
|
Shortcodes allow copy editors to continue using WordPress-esque features, Markdown keeps our developers happy, and our users don't have any of the database overheads. It's win-win!
|
|
|
|
---
|
|
|
|
This is an extract from our [technical launch post](https://www.tomango.co.uk/thinks/tomango-progressive-web-app/).
|