This fixes an issue where an `<aside>` element with a single line would
look really weird and boxed in, compared to an `<aside>` element with
multiple lines.
This has been bugging me for a while and I finally looked up how
Benjamin Hollon handles this on his blog. Here's a good example:
https://benjaminhollon.com/musings/wireless-is-a-lie/
. When compared with my own blog, I noticed the additional `<p>` tag in
Ben's code and everything became clear. If we have multiple lines, Hugo
will automatically introduce paragraphs and the formatting will be
correct. For a single line however, Hugo would assume that it was part
of the content surrounding it. That's why the surrounding box of an
`<aside>` element with a single line would look squashed.
This makes it easier for theme users to add elements to the head. A file
located at layouts/partials/hook_head_end.html in the site folder will
override the (empty) `hook_head_end.html` in the theme.
This is a new feature in readable.css 1.1.0. The new version of
readable.css defaults to a navbar without animations, but to stay
compatible with older releases of this theme, we default to "classy"
instead which is the animated navbar.
The new navbar styles also look better without wrapping the elements
inside a `<span>`, so we make that conditional and only apply it when
the "classy" style is chosen.
This adds a workflow and accompanying script to update readable.css. The
script gets the latest tag version from the readable.css repository on
codeberg.org and compares it to the currently used version. If the
versions don't match up, we download readable.css and readable.min.css
from Codeberg and update layouts/partials/head.html.
* Update to readable.css v1.1.0
data-style="classy" was also added to the <nav> element to preserve the
same style as the previous default.
* Use minified version of readable.css to save bandwidth
The readable.css file is kept for readability sake of people using this
template.
---------
Co-authored-by: Benjamin Hollon <me@benjaminhollon.com>
The initial statement was wrong. There's no preferred way of doing
things.
Blockquotes are meant to hold actual quotes, whereas the aside element
can be used to signify content that is slightly off-topic in regards to
the rest of the post.
The README has been updated to show a code example of both, including an
exemplary screenshot.
Since Hugo 0.55, we have to use `markdownify` in shortcodes that contain
HTML elements. At least we have to, if we want to render markdown code
inside the HTML element.
To use the `<aside>` element, we have to wrap our content in an
`<article>` tag.
This fixes#4.
Co-authored-by: Robert Lützner <robert.luetzner@iternity.com>
Previously when we clicked on a tag link, it would append the path to
where we currently were, e.g. clicking "tag" on a post in the `/posts/`
lists, would send us to `/posts/tags/tag` instead of `/tags/tag`.
This fixes#7.
Co-authored-by: Robert Lützner <robert.luetzner@iternity.com>
This will display a favicon for the website. Favicons are cute little
icons that will show up on tabs in your browser, e.g. GitHub's mascot.
They can easily be generated by using online tools, e.g.
https://realfavicongenerator.net/
The resulting package only has to be downloaded and extracted into the
'static' directory of a Hugo website that is using this theme.
The path can then be set as follows in the config.yml:
```yaml
params:
favicon: favicon.ico
```
This fixes#3.
Co-authored-by: Robert Lützner <robert.luetzner@iternity.com>
Robert Lützner
Eamon Caddigan
CJ
Alice
Benjamin Hollon
CJ