* feat: add commento block
Signed-off-by: Kirill K <kovalev.kirill.a@gmail.com>
* fix: use params section in config example
Signed-off-by: Kirill K <kovalev.kirill.a@gmail.com>
* fix: use defer to execute script after page load
Signed-off-by: Kirill K <kovalev.kirill.a@gmail.com>
* Create fr.toml
French translation
* Social link to "mastodon" added
* Some statics partials are cached, to optimise rendering
* Caching moved so that the i18n menu will work as expected. Refs #35
In English, the translation that is supposed to be shown on top of the table of contents looks like this:
```toml
[whatsInThis]
other = "What's in this {{.Type }}"
```
When it is invoked, there are two mistakes: `{{ i18n "whatsInThis" humanize .Type }}`.
The first mistake is that you cannot call `humanize` in this context. The more severe one is that if you remove `humanize` it will pass the `.Type` directly to the i18n and that tries to extract `.Type` from it.
* Open social media in new tab and add Medium
svg file pulled from Medium post on their logos
and brand guides dated Aug 22, 2017
https://medium.design/logos-and-brand-guidelines-f1a01a733592
* Add new-window accessibility icon for social media icons
Visible on-hover of link-transition class, this PR also
adds a description to the social media icons indicating that
they will open in a new window.
This way, users will be able to see and hear (via a reader)
when a tab will open in a new window.
This approach is based on the one outlined here:
https://medium.com/@svinkle/why-let-someone-know-when-a-link-opens-a-new-window-8699d20ed3b1
via PR #134 @looer
Added config variable so this doesn't show up
Show "reading time" and "word count" but only if one of the following are true:
1) A global config `params` value is set `show_reading_time = true`
2) A section front matter value is set `show_reading_time = true`
3) A page front matter value is set `show_reading_time = true`
2.0 Enhancements
- Improve template structure
- Fixed issue where flexbox was configured improperly and the side column expanded with longer content.
- No longer assume that posts are called "post"
- Simplify tag handling
- Improve related posts handling
- Support native Table of contents (if declared in params)
- Add DISQUS commenting (if disqusShortname added to config)
- Uses Hugo's Related content feature
- Add asset hashing to Webpack for performance
Let's say your `.Site.Title` is "My Website". The code grabs `.Site.Title`, and then then checks to see if there's a `.Title`. When you're on the homepage, `.Title` is equivalent to `.Site.Title`, so that the browser bar will read:
> My Website | My Website
If we qualify `.Title` by confining to the `.Params` namespace, then the site title isn't duplicated:
```<title>{{ block "title" . }}{{ .Site.Title }} {{ with .Params.Title }} | {{ . }}{{ end }}{{ end }}</title>```
> My Website
But it still picks up `.Title` from posts and pages, where a content title exists in front matter:
> My Website | About Me
