# Hugo
# Navigation
# Build commands for Hugo.
npm install to install all the Hugo stuff.
npm start to start local Hugo server. Auto refreshes when files are changed.
npm run build to build production-ready site - site gets placed in “public” folder, which can be used to host the site.
# Content
All pages are stored in the content folder. The folder structure matches the site structure. All files are .md files but contain HTML almost exclusively.
# Assets
Images that need to be processed (e.g. referenced by the figure shortcode to generate responsive srcset image mark-up) need to be stored in assets/images. Assets that are referenced directly in your page can either be placed in the content folder at the same level as the file that’s referencing it, or in static/assets
# Layout
In the layout folder you’ll find all the templates for whole page layouts, partials (e.g. header and footer) and shortcodes for individual blocks/patterns.
# Shortcodes
We’ve used shortcodes to manage repeatable blocks on the page (pattern-based approach) where possible. To edit the mark-up for a shortcoded element you can find the shortcode files in the layouts/shortcodes. Name of the shortcode files match the name of the shortcodes in the mark-up.