My hawksworx.com blog site, powered by Hugo and Netlify
JavaScript CSS HTML
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
content citc pro night Apr 29, 2018
data
functions yarnify Feb 24, 2018
layouts
src
static citc pro night Apr 29, 2018
themes/simple-starter markdown fix Apr 10, 2018
.env-sample Let Hugo get git env vars directly from Netlify Feb 27, 2018
.gitignore more ignoring Mar 12, 2018
.nvmrc boostrapping the hugo version from a WIP Nov 7, 2017
README.md typos and links fixes Feb 11, 2018
config.yml gitinfo removed for now Nov 15, 2017
gulpfile.js expose a shortcut to opt in or out of a split test branch Feb 28, 2018
netlify.toml webconf redirect Jun 8, 2018
package-lock.json basic gravatar support to comments Feb 12, 2018
package.json
yarn.lock

README.md

hawksworx.com

Phil Hawksworth's blog. Served up at https://www.hawksworx.com and hosted on Netlify

Overview

This site is comprised of static files generated by Hugo for simplified deployment and hosting. It uses Gulp to automate some build optimisation tasks and to improve performance.

Environment installation

To build the site you need:

To setup the build environment, clone the repository and then in the working directory run: npm install to install any node modules required by the build.

The site can then be built via npm with the command:

npm run build

Deployment

The build command above will generate a set of static assets in a dist folder which can be deployed to any web hosting service.

My preferred method is to host on Netlify who can also run this build process in their own CI environment and then depliy teh build to their distributed CDN. Such deployments are triggered automatically by every git push to the master branch of the origin repository.

Development

To develop the site locally, run:

  • npm run watch to monitor and regenerate all Sass code automatically
  • hugo server --disableFastRender to monitor and rebuild the entire site automatically (and reload the local site)

other commands

npm run cards at the end of the build process (npm run build) but can be invoked separately of desired. This generates image assets based on a special "card" output format for every page in the site. The images are copied to the dist/images directory and are referenced as an Open Graph asset in each page in order to be served as Twitter cards and open graph assets omn Facebook.