| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |
|
|
|
|
|
| |
This reverts commit f99133842b48dc7d99e577df37e34ea143f1eeaf. We have
found this solution to introduce other (worse) problems because the
padding is unconditional. For now do not apply any special style to
<code>.
|
| |
|
|
|
| |
We don't need to reference the block name in the 'endblock' statement if
blocks are not nested.
|
| |
|
|
|
|
| |
The first post has information on what to expect from this site. Since
it will scroll further and further down, make sure we reference it for
quick access.
|
| |
|
|
|
| |
This was still missing from here. Whilst we're here, slightly reword a
sentence.
|
| |
|
|
|
| |
These elements overflow on smaller screens, so make sure that they're
getting scrollbars.
|
| |
|
|
|
| |
This was missed in f28cb70 (templates: Make page titles mandatory,
2021-06-16).
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This removes a branch from the template and also makes sure that screen
readers and similar software still get access to the post title even if
we want to hide it on the presentational layer.
|
| |
|
|
| |
This improves the readability and consistency of the CSS.
|
| |
|
|
|
|
| |
Users with narrow displays currently have to deal with post banners that
do not collapse nicely. This commit adds some padding to the tag list
and hides the post time on smaller resolutions.
|
| |
|
|
|
|
|
| |
Currently we allow empty post titles, gracefully falling back to a
default value. This increases complexity somewhat. Since we think we'll
always be able to think of a title for a post, make it mandatory for now
to provide one.
|
| |
|
|
|
|
|
| |
Instead of using boolean arguments to control the article class (and
which parts of the article are rendered), accept a class string that is
used directly. For now, check for the right class before rendering a
title - an upcoming commit will change this to be cleaner.
|
| |
|
|
| |
This feature was only used once for testing.
|
| |
|
|
|
| |
We can get rid of the post title in the banner since the base template
now renders it in the main banner whenever we show a single post.
|
| |
|
|
| |
This makes the HTML source slightly nicer.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, we pad certain elements with manual interpunct spacers that
are defined in the templates themselves. This is suboptimal for a number
of reasons. Templates should be used for textual or semantic data, not
presentation. Additionally, we have no good control over how whitespace
characters will end up being rendered. Adding or deleting spacers is a
nightmare.
To fix this, use CSS to render spacers instead. To that end, introduce a
couple of HTML elements in the top banner and keep supplementary links
in a list inside a <nav> element. Add a spacer mixin that can be applied
to any element that needs it.
|
| |
|
|
|
|
|
|
|
| |
Currently we show the slogan both on the index as well as all sub-pages.
This needs some special handling in the template, since the page
description for the index is empty (the slogan takes its place).
Simplify the template further by making sure description is always set,
and set it to the slogan only on the index page.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the first in a series of commits that will attempt to clean up
and simplify the templates, most of which were put together hastily.
One particular egregious example of this is how Tera blocks are employed
to set per-page titles, provide banner descriptions and links, and
include additional RSS feeds. These elements are all outside the normal
'content' block provided by the base template. Almost always they
contain only one line of text.
This solution was chosen because there did not seem to be a cleaner way
of having per-page variables in the base template. This is a problem
especially for the 'single' and list' taxonomy pages which do not even
have front matter (and therefore cannot carry additional metadata).
Furthermore, we want to keep each page's front matter as minimal as
possible and avoid hard-coding a post description of "post № <X>".
Instead rely on the fact that each type of page is identifiable in the
base template by the variables that are set in it. The index carries the
'section' variable, pages carry 'page', a single taxonomy term carries
'term', and a single taxonomy carries 'terms'.
Using this information we can consolidate all these blocks into the base
template in a simple and clean way.
|
| |
|
|
| |
This invocation might otherwise be confused with 'git branch -D .'
|
| |
|
|
|
|
| |
Currently, --font-mono is only applied to <pre> blocks, leaving <code>
unstyled. Since <pre> blocks will end up containing <code>, set the font
family on <code> instead.
|
| | |
|
| |
|
|
|
| |
Due to the density of the fonts used, <code> blocks tend to be too close
to the normal text. Add some padding to mitigate.
|
| | |
|
| | |
|
| |
|
|
| |
This way we do not have to specify the color in its selector.
|
| |
|
|
|
|
|
|
|
|
|
| |
Post titles are currently only visible in the feed, or on the post page
itself. Since people may remember posts by their titles rather than
their number, display the titles on each post's banner as well for
easier searching. This means we can now get rid of the extra item in the
post page's description.
A neat side effect is that we now have a header element for each
<article>, making W3C a bit happier.
|
| | |
|
| |
|
