Introduction Download hugo-extended Find a theme hugo new site git sub module copy config.toml, and adjust settings. Commit Make Netlify aware We have these folders locally: And yet on GitHub, a shorter list: From burntfen, we read: Wait, so why weren’t the other folders - archetypes, content, data, layouts, static - added? Well, they’re empty. Hugo likes empty folders. Git doesn’t. If you want to keep them, you’ll need to add a file into each of them. 
Experiments with static sites
Reviewing static site generators and choosing Hugo
Introduction I plan to write more fully on static sites, particularly covering: exporting from WordPress hosting with AWS S3, Azure Storage Accounts, and Netlify adding in Content Delivery Networks JAMStack sites like Gatsby a CI/CD workflow speed comparisons Benchmarking The assumption is that the move to a static site would be faster than an uncomplicated WordPress site. Choosing Hugo Much of the inspiration (and many of the steps) were borrowed from Christian Bär’s blog posts on setting up a static site 
Writing with Markdown and Git
Introduction In three recent roles (two paid, and one voluntary), I estimate that I’ve written 300 or so internal technical and procedural documents using Atlassian Confluence. When I left a recent role, a colleague was kind enough to give me a book - How to Make a Living with Your Writing, which has prompted me to at least start writing in a more structured way. I want to be able to make use of smaller snippets of time, so I’ve spent some time thinking about which tools will allow me to write quickly, without forcing me to use a different tool simply because I’m writing a blog post as opposed to a chapter of a technical book.