Zola 0.19.0 changed the config options related to RSS/ATOM feed
generation, allowing multiple feeds at once. This patch addresses this
change and adds as many links in the HTML head as there are feeds.
Fix#64
There's some css rules for which prepending the name of the menu item as
set in the config causes the <a> element to appear shifted down compared
to the other <a> elements of the menu. I might have a look later, but
for now this enables only the appeareance of the RSS icon, discarding
entirely the name of the link.
This adds support for showing a tiny RSS svg badge in the top menu in
case the user added a menu_item that looks like this:
`{name = "", url = "$BASE_URL/$FEED_FILENAME"}`
This also requires that the user has a config.toml that contains the
following entries:
generate_feed = true
feed_filename = "rss.xml"
author = "your name here"
This is to improve Google indexing pages, for the /tags/ page. In GitHub
Pages, the URL /tags does not exist per se, but is a redirect to /tags/.
Google Crawler gets confused with 301 HTTP status and does not index it.
Zola v0.18 added an option to set all images with `decoding=async` and
`load=lazy`, but this only applies to `<img>` tags generated from
Markdown `![]()` syntax. This patch adds these attributes by default to
`figure` and `image` macros.
This fix works by adding missing two missing `.extra`'s when accessing the `logo_home_link` in the `header` template block.
The bug is caused by the first missing `.extra`, which makes Tera assume that `logo_home_link` variable doesn't exist, so the `if` trigger for using it never fires. This means that the logo will always link to the default value of `base_url`.
The second missing `.extra` comes after the `if` fires. It's used to set the value of `logo_link` to `logo_home_link`.
* Noting that (as of 0.14) zola does not pass much of a context when
rendering the 404 page, so things like current URL/path aren't
available
* To work around this the `menu` macro has been split into `menu_for`
which accepts a parameter for which item is active.
* The previous macro continues to work as is, forwarding the results of
figuring out which item is active to the new `menu_for` macro
* The added 404 page will then use the `menu_for` macro and pass in a
blank item
