Skip to content

feat(design): blog page redesign, teal footer and pixel-font review round - #556

Open
Totara-thib wants to merge 4 commits into
mainfrom
feat/blog-redesign-new-footer
Open

Totara-thib wants to merge 4 commits into
mainfrom
feat/blog-redesign-new-footer

Conversation

@Totara-thib

Copy link
Copy Markdown
Contributor

What changed

Designer review of 2026-11-17 (Figma Blog-Black frame 2698:4501, Docs_Getting-Started_OK, and the "Commentaires - Plumber" document).

Blog index (BlogIndexLayout2.astro, new PostFeatured.astro and PostRow.astro)

  • Pixel-font category filters over a stroke.
  • The newest matching post is featured: image on the left, tag, date, title, lead and "Learn more" on the right.
  • The other posts are full-width rows (title, lead, pixel category and date) that turn accent blue on hover.
  • Figma pagination row: 10 per page by default, per-page select, "1–10 of N", page select and prev/next.
  • Filter, page and per-page state live in the URL (?category=, ?page=, ?per=); every post stays in the HTML.

Footer on every page (Footer.astro, FooterLink.astro, footer-pixel-band.svg)

  • Accent-blue block under a band of 60px pixels copied from the Figma vector; the band scales with the page width so the squares stay square.
  • Pixel-font column titles and legal row, bordered newsletter field, five pixel social icons (GitLab and Discord added, in the Figma order; GitLab links to the catalog page).
  • Link data is unchanged: the Figma mock-up lists "App" and "Insights", which have no page yet.

Site-wide review items

  • Page titles grow from 54 to 62px (.h1, .docs-h1), eyebrows from 22 to 24px.
  • Every button uses the HaxrCorp pixel font: 24px on the site, 20px in the navbar.
  • The navbar GitHub icon is the pixel one; the social icon set is refreshed from the new footer.

Docs

  • Pixel GitHub and GitLab icons on the provider cards.
  • Pixel shield on the "tip" aside.
  • Community & support cards: pixel chat and mail icons, larger pixel chevrons, 8px outer corners, accent hover with near-black text.

Content

  • The designer's "20 minutes / 23,000 projects" visual replaces the hero of the tj-actions post (JPEG, 2048px, from the Figma file at full resolution).

Reviewer notes

  • Figma has no mobile frame for the new footer or the blog page; the phone and tablet layouts are adaptations of the desktop frame (two link columns, then newsletter, socials, legal row and wordmark; featured text under its image; row labels under the row text).
  • Checked in Chrome at 390, 820, 1440 and 1920px: blog index (filters, page 2, hover), blog post, archive, home, docs getting-started, footer.
  • npm run lint and npm run build pass.

…ound

Figma review of 2026-11-17 (Blog-Black frame 2698:4501, Docs_Getting-Started_OK, the
designer's comments document):

- blog index: pixel category filters, the newest match featured (image left, text right),
  the other posts as full-width rows that turn accent blue on hover, ten per page with the
  per-page and page controls; state in the URL, every post still in the HTML
- footer on every page: accent-blue block under a scaling band of 60px pixels, pixel-font
  titles and legal row, bordered newsletter field, five pixel social icons (GitLab and
  Discord added), the wordmark in near-black
- site-wide: page titles 62px, eyebrows 24px, buttons in the HaxrCorp pixel font (24px,
  20px in the navbar), pixel GitHub icon in the navbar
- docs: pixel GitHub and GitLab icons on the provider cards, pixel shield on the tip aside,
  community cards with pixel chat and mail icons, larger chevrons and the accent hover
- the designer's hero image for the tj-actions post
@github-actions

github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

Preview deployment for 5716c4a: https://getplumber-2am5hlbf8-getplumber.vercel.app

Resolves GHSA-r3h5-4585-7x3w (moderate): the @astrojs/node image endpoint could read
files from a case-variant sibling of the output directory. Lockfile regenerated with npm 10
from the registry, as the README prescribes.
…a specs

Designer review of 2026-11-18 ("Corrections Plumber Blog"):

- blog header 1008px wide so the lead stays on one line
- filters: 34px tall, 14px apart, #5C6262 stroke at 50% over a 5% fill
- featured post: 872/424 columns, tag with the same stroke and fill in the
  grey, date in white, a #8D9596 25% rule 24px under the tag row, 24px to
  the 32px Regular title, 32px to the six-line lead
- list rows: titles in the Figma grey, 250ms hover like the home rows,
  #8D9596 25% rules
- pagination 88px under the list: 38px selects with the grey stroke and
  fill, 14.4 x 8 pixel chevrons, controls 32px apart
- chevron links everywhere (.link-arrow): Regular text, 6 x 10.8 pixel
  chevron, underline 10px under text + chevron; used by "Learn more", the
  release archive link, the home "Plumber Scan" link and the docs
  "All install methods" link (new LinkArrow MDX component)
- grayscale font smoothing so Inter and the pixel font no longer render
  heavier than the Figma rasteriser on the dark background
Figma "Plumber - Website - Ready", frame About us 2728:4912, measured
layer by layer (CSS export of the frame) on 2026-11-18:

- hero: eyebrow, 62/112 title on 1087px, two 18/160 paragraphs beside
  the 327px facts list, the three-cell numbers strip 124px lower
- story: title block, the 1320 x 726 team photo (black and white),
  three story blocks in 312px and 650px columns
- beliefs: the #49B4B8 band (120px/107.5px padding, 62px Medium title)
  and the four 312px rule cards with 92px pixel numbers
- team: 872px list of 128px rows that turn accent on hover and open to
  the bio and the 312px portrait (Figma component variants)
- "Backed by." paragraph at 38/110 with the white runs of the design
- two closing calls to action behind 4px dashed rules, 269px above the
  footer band
- sections 280px apart, copy and portraits in config/en/aboutData,
  "About us" link enabled in the navbar
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