🏗️♻️:tidy two seams in the stylesheets - #1839
Merged
Merged
Conversation
74px was written in three files: the page offsets itself by it, the navbar's links fill it, and the toggler wrapper matches it. Three copies of a number that has to agree, and nothing to notice if one drifted. It lives with the palette now, which every stylesheet here is compiled after. The compiled CSS is unchanged, byte for byte. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5
The card naming the newest post used `.post-title`, `.post-meta` and `.post-date`, which are the news archive's names in _news.scss. Both files styling the same words is a trap: a rule written without the `.home` in front of it lands on the archive, which is how the archive came to be drawing its titles in a colour only the home page defines. It is the Latest card, so it is `.latest-*` now. No selector is shared between the two files any more. Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is> Assisted-by: Claude-Code:claude-opus-5
✅ Deploy Preview for gh-pages-openinf ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
OpenINFbot
approved these changes
Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two seams in the stylesheets, neither of which changes how anything looks.
The navbar's height, once
74pxwas written in three files:_custom.scssoffsets the page by it,_nav.scsssizes the toggler wrapper and the links to it,_home.scssreads itinto
--nav-h. Three copies of a number that has to agree, and nothing tonotice if one drifted.
It sits with the palette now, in
_sublime-theme.scss, which every otherstylesheet is compiled after.
The compiled CSS is byte-identical to
live. Verified by building both anddiffing
main.min.css, not by reading it.The front page's card, renamed
The card naming the newest post used
.post-title,.post-metaand.post-date. Those are the news archive's names, in_news.scss.Both files styling the same words is a trap, and it had already sprung once: a
rule written without
.homein front of it reached the archive, which is how/news/came to be drawing its titles in a colour only the home page defines.Scoping fixed the symptom; the shared names were still there waiting for the
next one.
It is the Latest card, so it is
.latest-*now:Checked afterwards: no selector at all is shared between
_home.scssand anyother stylesheet.
The Liquid is untouched —
collections: ['post']andcollections.postsarethe Eleventy collection, not CSS.
Checks
nps testpasses, all 17 verifiers.vnuclean on/and/news/. Confirmedin the built output that the home page emits
latest-*, the archive stillemits
post-*, and each file's rules still reach their own markup.