summaryrefslogtreecommitdiffstatshomepage
Commit message (Collapse)AuthorAgeLines
...
* content: Add new post: "proc(5) hidepid=2 and systemd"Wolfgang Müller2021-10-27-0/+35
|
* templates: Use a unitless integer for the img width attributeWolfgang Müller2021-10-19-1/+1
| | | | | | | According to MDN [1], the width attribute carries a unitless integer instead of "px" et al. Make sure we conform to the standard. [1] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#attr-width
* templates: Also set avatar size in HTMLWolfgang Müller2021-10-18-1/+1
| | | | | | | Legacy devices might not render the CSS correctly, making the high-resolution avatar images take up most of the space on the site. Make sure to resize them to 64px in HTML using a width attribute.
* sass: Draw a border around preWolfgang Müller2021-09-04-1/+3
| | | | | | Instead of just indenting the pre block, it is more visually pleasing and clear to draw a border around it. That way, code blocks are clearly delineated from text.
* templates: Fix permalink content for mentioned postsWolfgang Müller2021-08-13-1/+1
| | | | | | | | | | | | | | A regular posts indicates its permalink with a section sign. However, for mentioned posts we'd like to be explicit about the post number, since we may refer to them this way in the parent post. This behaviour should have been working since day one in ad2be2b (Initial commit, 2021-06-12), but it was subtly broken. Since the render_post macro does not have access to the 'mention' variable, only the section sign would ever be used to indicate a permalink. This probably happened because the rendering code for a post used to live in the post template instead of a macro.
* templates: Do not show exact post timesWolfgang Müller2021-08-13-1/+1
| | | | | | | | | | Now that about two months have passed since the initial publication, we know better with which frequency posts are made. Since there's usually more than one day between posts, rendering prominently the time at which posts were made is needlessly noisy. We already put the exact date and time in the HTML source and the title tag, so it is still there if really needed.
* content: Add new post: "Better hunk headers with gitattributes(5)"Wolfgang Müller2021-08-11-0/+50
|
* content: Add new post: "Trying out the Nikon D5200"Wolfgang Müller2021-08-09-0/+26
|
* templates: Render markdown in img's figcaptionWolfgang Müller2021-08-09-1/+1
| | | | | | | | | | The img shortcode inserts, along the picture itself, a figcaption element containing a brief description. We may want to include links or other HTML elements in that description. This is not possible right now because we insert the caption content verbatim. This commit changes the img shortcode such that markdown is now rendered inline for the figcaption element.
* content: Mention Maildir difficulties in post 8Wolfgang Müller2021-07-25-1/+4
| | | | | People might read post 8 on its own so make sure we mention the followup.
* content: Add new post: "git-am(1) and mail sorting"Wolfgang Müller2021-07-25-0/+35
|
* templates: Have the 'ref' shortcode use a.internalWolfgang Müller2021-07-25-1/+1
| | | | | | Added in the previous commit, this class renders a link more subtly and is supposed to be used when referencing internal content. We do exactly this here.
* sass: Add style for internal linksWolfgang Müller2021-07-25-0/+7
| | | | | | | | We may want a post to contain references to a whole number of previous posts. The styling for external links will then clash, especially if there are a lot of them. Make sure to make it possible to highlight internal links differently and more subtly by adding an "internal" class for <a>.
* Use h3 for "Mentioned posts"Wolfgang Müller2021-07-25-3/+3
| | | | | | | | | An upcoming post will (finally) make use of the "mentions" feature. Whilst working on that post we noticed that the header indicating mentioned posts is a big too big and clashes even with the site title. h3 should be better suited for this purpose. Since the default margins are slightly different from h2, make sure to tweak the stylesheet too.
* content: Add new post: "Applying patches with mutt(1)"Wolfgang Müller2021-07-23-0/+60
|
* content: Add new post: "Wrap-around search in less(1)"Wolfgang Müller2021-07-09-0/+41
|
* content/1: Link zunzuncito's git repositoryWolfgang Müller2021-07-06-0/+5
|
* content: Add new post: "Firefox and the Link HTTP header"Wolfgang Müller2021-07-03-0/+43
|
* templates: Allow passing format to img shortcodeWolfgang Müller2021-07-03-1/+1
| | | | | | | | Sometimes we may want to override the default setting when processing images. Furthermore, since we will most likely want to generate JPG files in the general case in order to minimise the amount of data transferred when opening the front page, have the default in the shortcode be "jpg" instead of "auto".
* sass: Decrease the size of the logo on small screensWolfgang Müller2021-06-27-0/+6
| | | | | This further increases the space available for text and makes the logo a lot less dominant.
* content: Add new post: "Use git-send-email(1) only to send"Wolfgang Müller2021-06-25-0/+49
|
* Revert "sass: Add some padding to <code>"Wolfgang Müller2021-06-25-1/+0
| | | | | | | 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>.
* templates: Simplify Tera blocksWolfgang Müller2021-06-24-4/+4
| | | | | We don't need to reference the block name in the 'endblock' statement if blocks are not nested.
* templates: Add "about" link to the first postWolfgang Müller2021-06-24-0/+1
| | | | | | 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.
* content/1: Add contact informationWolfgang Müller2021-06-24-1/+6
| | | | | This was still missing from here. Whilst we're here, slightly reword a sentence.
* sass: Have pre overflowWolfgang Müller2021-06-24-0/+1
| | | | | These elements overflow on smaller screens, so make sure that they're getting scrollbars.
* post.sh: Always set titleWolfgang Müller2021-06-24-1/+1
| | | | | This was missed in f28cb70 (templates: Make page titles mandatory, 2021-06-16).
* content: Add new post: "(Un)Blinking cursorsWolfgang Müller2021-06-17-0/+25
|
* sass: Apply margin to tags in the banner onlyWolfgang Müller2021-06-16-2/+3
|
* Use CSS to hide titles on single post pagesWolfgang Müller2021-06-16-1/+4
| | | | | | 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-13/+13
| | | | This improves the readability and consistency of the CSS.
* sass: Provide better rendering for narrow displaysWolfgang Müller2021-06-16-0/+16
| | | | | | 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.
* templates: Make page titles mandatoryWolfgang Müller2021-06-16-3/+3
| | | | | | | 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-9/+5
| | | | | | | 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-5/+0
| | | | This feature was only used once for testing.
* templates: Only render post title in the feedWolfgang Müller2021-06-16-3/+3
| | | | | 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-20/+44
| | | | | | | | | | | | | | 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: Do not show slogan on all pagesWolfgang Müller2021-06-16-6/+5
| | | | | | | | | 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.
* templates: Consolidate blocks into base templateWolfgang Müller2021-06-16-38/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* content/3: Delete final full stopWolfgang Müller2021-06-15-1/+1
| | | | This invocation might otherwise be confused with 'git branch -D .'
* sass: Specify font family for <code>Wolfgang Müller2021-06-13-2/+1
| | | | | | 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.
* content: Add new post: "Patch workflows and git branch -d"Wolfgang Müller2021-06-13-0/+31
|
* sass: Add some padding to <code>Wolfgang Müller2021-06-13-0/+1
| | | | | Due to the density of the fonts used, <code> blocks tend to be too close to the normal text. Add some padding to mitigate.
* sass: Use lighter color for --fg-href in dark modeWolfgang Müller2021-06-13-1/+1
|
* content/2: Simplify wordingWolfgang Müller2021-06-12-4/+4
|
* templates: Set mute class on banner's <h2>Wolfgang Müller2021-06-12-2/+1
| | | | This way we do not have to specify the color in its selector.
* Put post titles in the bannerWolfgang Müller2021-06-12-5/+12
| | | | | | | | | | | 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.
* content: Add new post: "Did you mean to go to..."Wolfgang Müller2021-06-12-0/+31
|
* Initial commitWolfgang Müller2021-06-12-0/+811
powered by cgit and git | oriole.systems | how to verify signatures