summaryrefslogtreecommitdiffstatshomepage
path: root/templates/macros.html (follow)
Commit message (Collapse)AuthorAgeLines
* Use CSS to hide titles on single post pagesWolfgang Müller2021-06-16-1/+1
| | | | | | 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.
* Use "title" class for the header in the bannerWolfgang Müller2021-06-16-1/+1
| | | | This improves the readability and consistency of the CSS.
* templates: Make page titles mandatoryWolfgang Müller2021-06-16-1/+1
| | | | | | | 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.
* templates: Pass article class in render_post macroWolfgang Müller2021-06-16-7/+3
| | | | | | | 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.
* Remove special handling for draft postsWolfgang Müller2021-06-16-1/+0
| | | | This feature was only used once for testing.
* templates: Only render post title in the feedWolfgang Müller2021-06-16-2/+2
| | | | | 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.
* templates: Fix up some issues with whitespace controlWolfgang Müller2021-06-16-4/+4
| | | | This makes the HTML source slightly nicer.
* Use CSS to add spacersWolfgang Müller2021-06-16-1/+1
| | | | | | | | | | | | | | 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.
* templates: Set mute class on banner's <h2>Wolfgang Müller2021-06-12-1/+1
| | | | This way we do not have to specify the color in its selector.
* Put post titles in the bannerWolfgang Müller2021-06-12-2/+3
| | | | | | | | | | | 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.
* Initial commitWolfgang Müller2021-06-12-0/+43