summaryrefslogtreecommitdiffstatshomepage
path: root/scss/style.scss (unfollow)
Commit message (Collapse)AuthorLines
2020-06-13css: Move custom properties to their own fileWynn Wolf Arbor-34/+1
In preparation for making man.css respect prefers-color-scheme, move all custom properties to their own file so they can be included easily.
2020-06-13css: Use dark colours when prefers-color-scheme indicates dark modeWynn Wolf Arbor-0/+13
2020-06-13css: Set the blockquote foreground colour explicitlyWynn Wolf Arbor-0/+1
This element's foreground colour is inherited from the root element. Since we use a special background colour here, make sure to explicitly set the foreground colour in conjunction.
2020-06-12css: Add colour variables for anchor elementsWynn Wolf Arbor-0/+10
Currently we use the default colour for these. In preparation for prefers-color-scheme, add two variables containing the default colours for normal and visited anchors.
2020-06-12css: Introduce variables for various coloursWynn Wolf Arbor-7/+12
Currently, colours are set per element. In preparation of the support of prefers-color-scheme, use variables instead so they can be modified in one place.
2020-06-12css: Remove superfluous definitionWynn Wolf Arbor-1/+0
This particular background colour will be inherited from the root element and does not need to be defined explicitly.
2020-06-12css: Use CSS custom properties instead of Sass variablesWynn Wolf Arbor-17/+20
In preparation for the support of prefers-color-scheme, convert all presently used Sass variables to CSS custom properties. This will enable us in an upcoming commit to define different values per media query. While at it, use a better name for variables holding colours.
2020-06-06Attempt a thorough redesign of the landing pageWynn Wolf Arbor-65/+62
After careful consideration we have decided to replace the more brutalist landing page with something simpler and more in line with the styling of the actual posts. Have the front page include a short introduction and some further links to the atom feed and git.oriole.systems. Use a more traditional and simple top-to-bottom layout for the article links in lieu of the more idiosyncratic left-to-right list that was difficult to scan for some people. Keep the post styling as is, but move around and change a few HTML elements to make more semantic sense and improve the clarity of the CSS.
2020-06-01css: Highlight current target in the footnotes blockWynn Wolf Arbor-0/+4
When clicking on a footnote reference, the browser scrolls all the way down to the footnotes block of the post. It is not immediately clear which footnote was referenced, so use the `:target` selector in the footnotes block to make the linked footnote bold.
2020-06-01css: Reduce font weight for footnote referencesWynn Wolf Arbor-1/+0
In fde2230 (css: Add styling for footnotes) we introduced styling for footnote references, removing the underline and making them bold. However, as pointed out by a user, having them bold makes them less readable and clear. Therefore, reduce the font weight back to normal.
2020-05-31css: Add styling for figuresWynn Wolf Arbor-0/+13
The figure (and figcaption) elements have not been used before. The upcoming post will include them, and this commit adds a bit of styling to make them look nice. Use a more muted color and a smaller font for caption text itself and provide a "round" class for any image element in a figure, which should help with making darker images less jarring.
2020-05-31css: Add styling for footnotesWynn Wolf Arbor-0/+9
The upcoming post is the first one to include footnotes. This commit adds a bit of styling for them. The footnotes block at the end of the post is a bit too prominent compared to the rest of the post. Use a smaller font size to make it stand out less. Footnote references in the text are anchors and therefore underlined by default. Remove any text decoration from them and make them easier on the eyes.
2020-05-31css: Improve styling of the horizontal rule elementWynn Wolf Arbor-3/+2
This element has not been used before at all, but the upcoming post will be including it it in the footnotes block. Use a more fitting double-border style instead of the questionable design from the initial commit.
2020-04-11css: Use a custom font-size for codeWynn Wolf Arbor-2/+4
We found 'smaller' to be too small, so go with 85% for now.
2020-04-11css: Add indent and clear pre stylesWynn Wolf Arbor-0/+13
This commit adds two new classes for <pre> tags: 1) pre.clear overrides the standard canary background color with white 2) pre.indent defines a <pre> tag that is indented and marked with a border These classes are mainly meant for preformatted content that has been added manually and should not be styled like the common code blocks.
2020-02-21css: Adjust font sizes and line heightWynn Wolf Arbor-1/+5
These should make the pages more comfortable to look at.
2020-01-12css: Remove unnecessary quotingWynn Wolf Arbor-1/+1
2020-01-12css, templates: Remove footerWynn Wolf Arbor-5/+0
This element had no purpose and was taking up 200px for no reason.
2020-01-12css: Improve readability by increasing the line heightWynn Wolf Arbor-1/+2
Add a bit more space to paragraphs, whilst contracting pre-formatted content (which mostly is code and uses a different font which does not need this kind of space).
2020-01-11css: Tweak canary colorWynn Wolf Arbor-1/+1
2020-01-11css: Make content in <pre> more readableWynn Wolf Arbor-1/+3
This commit changes the background color of <pre> to be a bit less colourful, and changes text color from pure black to a slightly tinged black to increase readability.
2019-09-09css: Remove unused pre.poetry ruleWolfgang Müller-6/+0
2019-08-02css: Improve visibility of a focused nav.main elementWolfgang Müller-0/+5
Previously the only indicator was the standard :focus outline rule, this should make the focused element on the main page very clear.
2019-07-22css: Add rules to keep images within page boundsWolfgang Müller-0/+2
powered by cgit and git | oriole.systems | how to verify signatures