Initially, when I started my Blog journey, I was enthralled by this very theme and I am using it since. However, original developer has ceased maintaining the theme and it is riddled with many bugs. Hence, I have taken upon myself to maintain this theme.
I fully intend to keep the essence of the theme as-it-is and only add minor updates and squash bugs which may arise.
The example config file can be found in the theme’s exampleSite folder. You can just copy the config.toml to the root directory of your Hugo site. There are instructions in the example config file, feel free to change strings as you like to customize your website.
Keep your regular pages in the content folder. To create a new page, run hugo new page-title.md
Keep your blog posts in the content/posts folder. To create a new post, run hugo new posts/post-title.md
In Hugo, layouts can live in either the project’s (root) or the themes’ layout folders, any template inside the root layout folder will override theme’s layout that relative to it, for example: layouts/_default/baseof.html will override themes/hermit/layouts/_default/baseof.html. So, you can easily customize the theme without edit it directly, which makes updating the theme easier. Here’s some common customizations:
Customize social icons
You can modify or add any svg icons in site’s layouts/partials/svg.html.
Customize comment system
We only have built-in support for Disqus at the moment, if that doesn’t fit your needs, you can just add html to site’s layouts/partials/comments.html.
Add custom analytics
If you prefer to use different analytics system other than google analytics, then add them inside layouts/partials/analytics.html.
If you’d like to customize theme color or fonts, you can simply override assets/scss/_predefined.scss, by simply copy it to site’s root (keep the same relative path) then edit those variables. But keep in mind, you’ll need Hugo extended version which has the ability to rebuild SCSS. You don’t have to use extended version in production but in this case it’s necessary to make sure the resources folder is committed and “up to date” (by running hugo or hugo server locally using the extended version). But anyway, always use the extended version if you can.
For adding other custom CSS to the theme, you can assign an array of references in config.toml like following:
You may reference as many stylesheets as you want. Their paths need to be relative to the static folder or it can be a full URL for external resources.
You can inject any html code to every page’s document head or right above the closing body tag. This makes it easier to add any html meta data, custom css/js, dns-prefetch etc. To do this you simply need to create a file at site’s layouts/partials/extra-head.html or layouts/partials/extra-foot.html, code inside will be injected to every page.