Skip to content

🏗️♻️:tidy two seams in the stylesheets - #1839

Merged
openinf-commit-queue[bot] merged 2 commits into
livefrom
chore/tidy-stylesheet-seams
Aug 21, 2026
Merged

🏗️♻️:tidy two seams in the stylesheets#1839
openinf-commit-queue[bot] merged 2 commits into
livefrom
chore/tidy-stylesheet-seams

Conversation

@DerekNonGeneric

Copy link
Copy Markdown
Member

Two seams in the stylesheets, neither of which changes how anything looks.

The navbar's height, once

74px was written in three files: _custom.scss offsets the page by it,
_nav.scss sizes the toggler wrapper and the links to it, _home.scss reads it
into --nav-h. Three copies of a number that has to agree, and nothing to
notice if one drifted.

It sits with the palette now, in _sublime-theme.scss, which every other
stylesheet is compiled after.

The compiled CSS is byte-identical to live. Verified by building both and
diffing main.min.css, not by reading it.

The front page's card, renamed

The card naming the newest post used .post-title, .post-meta and
.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 .home in 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:

.post        -> .latest
.post-meta   -> .latest-meta
.post-cat    -> .latest-cat
.post-date   -> .latest-date
.post-body   -> .latest-body
.post-title  -> .latest-title
.post-excerpt-> .latest-excerpt

Checked afterwards: no selector at all is shared between _home.scss and any
other stylesheet.

The Liquid is untouched — collections: ['post'] and collections.posts are
the Eleventy collection, not CSS.

Checks

nps test passes, all 17 verifiers. vnu clean on / and /news/. Confirmed
in the built output that the home page emits latest-*, the archive still
emits post-*, and each file's rules still reach their own markup.

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
@netlify

netlify Bot commented Aug 21, 2026

Copy link
Copy Markdown

Deploy Preview for gh-pages-openinf ready!

Name Link
🔨 Latest commit 91c4999
🔍 Latest deploy log https://app.netlify.com/projects/gh-pages-openinf/deploys/6a8795a3bcb0d4000806804d
😎 Deploy Preview https://deploy-preview-1839--gh-pages-openinf.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@OpenINFbot OpenINFbot added the commit-queue Land this pull request when its checks pass label Aug 21, 2026
@openinf-commit-queue
openinf-commit-queue Bot merged commit 26ebee2 into live Aug 21, 2026
15 checks passed
@openinf-commit-queue openinf-commit-queue Bot removed the commit-queue Land this pull request when its checks pass label Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants