Skip to content based on Hugo, Wercker, Prose, S3
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
wercker.yml marketing website based on Hugo. There is a full write up on the Atchai blog. This is just a standard Hugo project with the following modifications:

  • Custom theme in theme/atchai
  • Markdown content in /content
  • Static content (e.g. images) in /static
  • Hugo config in /config.toml
  • Werker config in /wercker.yml
  • config in /prose.yml
  • S3 redirect rules in redirects.xml

Getting Started

  1. git clone
  2. Install Hugo:
  3. Run local development server, watching filesystem for changes and live reloading in browser hugo server --watch --verbose
  4. Install npm modules by npm install
  5. Build js and css: gulp build
  6. To watch for sass changes, in another terminal, run gulp


# Generate assets w/ sourcemaps, and watch enabled
# Generate assets w/ sourcemaps, watch disabled
gulp build
# Generate assets w/o sourcemaps, for production deployments
NODE_ENV=production gulp build

SVG Pipeline

  • SVG Icons are generated by icomoon app (chrome extension here).
  • You may add more icons by unpacking ./misc/ and uploading selections.json in icomoon app.
  • It will load your currently selected icons in pack, allows you to add/update more icons.
  • When you're done, download svg zip from app, and place it in ./misc, rename the zip to

Usage is illustrated here.

Deployment Workflow

Wercker has been set up to generate the static site, then deploy to Amazon S3.

The site is currently automatically deployed to:

Adding / editing content with will connect to the Github repo, allow you to add/edit content of the site, and then commit these changes. Once your changes are committed and pushed, Wercker will automatically deploy.

  1. Go to
  2. Log into Github and select the appropriate repo
  3. You will land in the "/content" directory, can add or edit any file within here.
  4. Filenames are generated automatically from titles.
  5. URLs are generated in order of precedence from the URL metadata, then the filename.
  6. Images will be uploaded into static/images
  7. Use the "metadata" button on the RH pane to set the front matter.
  8. Use the "preview" button on the RH pane to check the formatting - this will not apply the real website theme.
  9. To publish, use the "save" button on the RH pane. Enter a short commit message to describe your changes.
  10. Wait approx 1 minute and the site will be rebuilt and deployed.
You can’t perform that action at this time.