This change adds overrides for text scale, color, alignment, and padding
in all layouts. This can be configured in site or page parameters, and
can target the default for all layouts (mostly useful for scale and
color), or for a specific layout (home, post, list, page, or terms).
The parameters are named in the following way: <type>_<style>:
- default_scale: Defines default scale for content (aka f5)
- default_color: Defines default color for content (aka mid-gray)
- default_padding: Defines default padding for content (aka ph*/pv*)
- default_align: Defines default alignment for content (aka tc/tj)
This can be overridden for "home", "post", "list", "page", or "terms" by
using instead of "default". If a type-specific style is not specified,
then it will fall back on "default", and if default is not specified, it
will fall back on the Ananke theme default.
Of course, theme users may put whatever classes they want in these
settings, but it still is valuable to specify what will be overridden
from the theme.
Previously the default date format (`January 2, 2006` ) was used for
blog and single page date visualizations.
The new parameter `date_format` can be used to override this format.
This allows the visualization of localized dates or a changed precision
(down to the minute or up to the month or year of publication).
Co-authored-by: Regis Philibert <login@regisphilibert.com>
The way relURL was used meant that one needed to preface the custom_css
entries with a slash, or the href would be incorrectly set to
subdircss/mycss.css rather than subdir/css/mycss.css, in the case of
a baseURL in a subdir.
Co-authored-by: Nick White <git@njw.name>
* 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>
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
