Page Comparison

...

• Place any JavaScript, images, and any other non-CSS assets in the static directory
• In your layouts/partials/ directory create templates that will be commonly used by other pages, for example, header.html and footer.html These will be referenced by other files using the partial keyword
• Create a layouts/_default/baseof.html template that contains general markup that will be used by every page
• Create a layouts/_default/list.html template which will be used by every section's index page in your site
• Create a layouts/index.html template that will be used by the home page
• Optionally create additional subdirectories in the layouts directory for any other section pages
• Once the layout templates are in place you can start adding markdown files in your content directory which will make up the majority of site maintenance work

It would be ideal if the majority of user managed content is authored solely using markdown with a minimal amount of shortcodes. One way of accomplishing this is by splitting up markdown files in the content directory, including a type property in the front matter, and then referencing that type property in layout templates where most of the markup can live.

Further Exploration

So far the Inclusive Cities and Social Justice Repair Kit projects have used Hugo to maintain content and only a subset of its features have been tested. As we use it for other projects we will most likely need to spend time trying out the following features:

• Hugo's multilingual support – it looks like translations live along side files for accompanying languages
• Search – Algolia provides free accounts to open source projects