The main features of this theme include:
* Page load speed optimizations (scores 98⁄100 on PageSpeed)
* Syntax highlighting with chroma
* Multiple categories as navigation tabs
* Tags and categories have their own pages
* Footer with variable social links and RSS
* Google analytics enabled
* Table of contents
If you have not already created a blog, I recommend you check out my getting
started guide for a comprehensive overview. Otherwise, just download it or clone it into
your themes/ directory:
$ cd themes && git clone https://github.com/aos/temple.git
Then reference it in your config:
theme = "temple"
Or when building the site, pass it in to the CLI:
$ hugo -t temple
Your config file will hold all your options:
baseURL = "https://aos.github.io/"
title = "Your Blog Title"
theme = "temple"
# If not set, it will not appear. Otherwise it will show below your footer links
copyright = "(c) 2008 - 2014"
# Enables Chroma-based syntax highlighting with theme "friendly"
# See https://xyproto.github.io/splash/docs/ for other theme options
pygmentsStyle = "friendly"
# If true, Chroma will highlight GitHub-style code fences in addition to
# highlight shortcodes
pygmentsCodeFences = true
# Enables the topmenu, which pulls from categories
topmenu = "categories"
# Enables custom date format (optional, the default is MM-DD-YYYY)
# For reference to date and time templating, see:
dateformatpretty = "2006-01-02"
# Enable table of contents, this can be overridden by page level parameter `toc`.
toc = true
# Builds a list page for each category given
tag = "tags"
category = "categories"
name = "Aos Dabbagh"
github = "aos"
email = "firstname.lastname@example.org"
gaid = "Your Google Analytics ID"
twitter = "twitterID"
medium = "mediumUsername"
There is also a fixed About page on the navbar. Create it using:
$ hugo new about
Contributions are welcome.
Features: If you are adding a feature, fork the repository, create a new branch
for your feature and submit a PR. Please make sure to put documentation for your
- Place a small comment about what your feature is doing above the code.
- If making additions that will affect the config file, make sure you update
the example config in README as well as the
Issues/Bugs: Submit a new issue with information about your issue and/or bug. If you
have a solution, then submit a new PR with the guidelines posted above in the
features section and link your issue to it using the keyword “closes”.