In the future new additions and changes will be assigned to version numbers rather than dates. This allows you to track changes in a better fashion. The state of this theme before this release has been assigned to v1.0.
This change requires Hugo v0.20 or greater due to the usage of new Hugo features.
The exampleSite
folder has become a standalone demo by modified the themesDir
property in the config.toml
. Make sure to comment out themesDir
in the config file if you use the theme in production. Read more
- Switch CDN for Mathjax due to retirement. See #86 (thanks @Heliosmaster)
- Prevent appearance of link for /posts on homepage. See dc62f88 (thanks @igor-sokolov)
- Block templates are now used to reduce redundancy. See 62d00ff
- Cache partials where possible. See d38e4be
- Add example for about page. See 183f569
- The
.Site.Params.mainSections
options allows you to specify which types of pages should be shown on the homepage. See 0928ac7 - Add
.Site.Params.gravatar
as a way use Gravatar for the profile picure. See b6b79b7
- The JSFiddle shortcode has been removed. See 5203108
With Hugo v0.20 the .Now
is deprecated and will be replaced by the now
template function. v0.19 does support both and as part of the transition phase. Hence the least required version of Hugo is v0.19.
You're now able to link local or external assets by adding their url to
the custom_js
and custom_css
variables in the config file.
The comment section can be disabled for single pages in the frontmatter.
The profile and the widgets can be disabled for single pages in the frontmatter. Are both disabled the content will use the full width of the page
This change adds the new variable avatar
under [params]
in the configuration. You need to set this path in order to show an avatar image. The default one can still be found under css/images/avatar.png
.
Hugo v0.15 is required in order to run the theme with the changes listed below:
The setup of Google Analytics changed slighty due to the switch to Hugo's built-in template. In order to update the theme you need to relocate thr google_analytics
variable in the configs and rename it to googleAnalytics
. Take a look in the example config.toml
.
Since the right shortcut of localization is "l10n" and not "i10n" (from internationalization) I renamed the shortcut in all places of the theme. The most significant change is the renaming of the i10n.toml
file inside the data
folder to l10n.toml
. This has the side effect that all key paths used for l10n changed within the templates too.