Testing HTML Elements
This post will contain a number of common HTML elements for the purpose of testing the CSS rules within the Typewriter theme.
This is a test of a link: a lot about Hugo
- First point
- Second point
- I thought a lot more about the third point
- Point #1
- Point #2
- Another epiphany of a third point
Coming into the world of Hugo, the biggest problem for me was piecing it all together.
- Hugo: You run Hugo locally on your machine, build and refine your site, add new content.
- Guthub: Github hosts repositories online. You create a repository on Github, then push your development build from your laptop when you’re ready to deploy it to the web.
- Netlify: Netlify is a radically cool hosting platform. It monitors your Github repository for new commits. When it finds new commits, it imports them, runs a Hugo build and hosts the resulting static site.
Hopefully that explains how all three pieces work together. Let’s walk through a typical Hugo/Netlify/Github deployment setup.
Build a local Hugo site
Let’s start with a local Hugo build.
hugo new site interweb
Why are we doing this? Because it helps us specify the Hugo version that Netlify will use to compile your site. If we prep this in advance, we don’t have to worry about it later. Example content is as follows - update your Hugo version to the latest:
[build] publish = "public" command = "hugo" [context.production.environment] HUGO_VERSION = "0.40.1"