Skip to content

📖✨:bring the news pages onto the site's design - #1844

Open
DerekNonGeneric wants to merge 1 commit into
livefrom
feat/news-redesign
Open

📖✨:bring the news pages onto the site's design#1844
DerekNonGeneric wants to merge 1 commit into
livefrom
feat/news-redesign

Conversation

@DerekNonGeneric

Copy link
Copy Markdown
Member

The news pages were the last two on the old design. /news/ read in a 48ch
column while the rest of the site reads at 1200px under an ink band, and the
category was a ribbon built from inset shadows, a ::before folded corner and
a ::after triangular point.

The archive

The newest post leads, and the rest follow as rows under "Earlier".

That split is the point. There is one post, and an archive containing a single
row looks like a mistake no matter how it is styled. Led by its newest entry,
the page reads as the news at one post and as an archive at fifty.

Every row carries the excerpt the post already had in its frontmatter and which
nothing had been rendering, so the page went from eleven words to seventy-nine
without anything new being written.

The post page

Its prose sits at a measure meant for reading. Its header takes the same ink
band as every other page, so the frame matches the site while the column inside
it suits the text.

The category

A flat chip, in two fixed pairs: dark teal on parchment for the light sections,
light teal on ink for the post header. Each pair clears AA on its own rather
than depending on what it happens to sit over, which is what lets the same chip
appear in three places without being checked three times.

Checks

nps test passes, all 17. Twelve foreground/background pairs computed against
true composited colour, the tightest at 4.88:1, all clearing AA.

Behaviour was verified at both sizes rather than reasoned about. With eight
posts: two pages, a featured post plus four rows on the first, correct pager,
prev/next resolving in both directions with the ends correctly one-sided, and
every class in both stylesheets rendering. With one post: the featured block
and the closing note, and the archive, pager and post nav all correctly absent.

Also

_includes/news-archive-item.liquid is deleted; nothing included it. Both
stylesheets were rewritten rather than adapted, because every class they
targeted was already dead — checked as exact class tokens across the built
site, not by substring.

The closing note under "Between posts" is the one piece of new prose here.

Noted, not done

Nothing uses .pagination, .page-link or .page-item now, so
bootstrap/scss/pagination may be dead weight in the bundle. Left for a
separate look rather than folded into a design change.

No feed yet.

They were the last two pages on the old design: a 48ch column where the
rest of the site reads at 1200px, and a category ribbon built from inset
shadows, a folded corner and a triangular point.

The newest post now leads the archive, and the rest follow as rows. The
split is what lets one post read as the news rather than as an archive
holding a single row, and it still reads as an archive once there are
fifty. Each row carries the excerpt the post already had in its
frontmatter, which nothing had been rendering.

The post page keeps its prose at a measure meant for reading while its
header takes the same ink band as every other page. The category is a
flat chip in two fixed pairs, one for the light sections and one for the
ink, so each clears contrast on its own ground rather than depending on
what it sits over.

Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is>
Assisted-by: Claude-Code:claude-opus-5
Assisted-by: Claude-Code:claude-fable-5
@netlify

netlify Bot commented Aug 22, 2026

Copy link
Copy Markdown

Deploy Preview for gh-pages-openinf ready!

Name Link
🔨 Latest commit 650e32a
🔍 Latest deploy log https://app.netlify.com/projects/gh-pages-openinf/deploys/6a89327797d9b000082691c0
😎 Deploy Preview https://deploy-preview-1844--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.

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.

1 participant