The public blog

A reading experience built for one audience — full-bleed hero, sticky contents rail with reading progress, share buttons, and a closing banner that opens the demo form in place.

What it is

The public /blog index and /blog/[slug] article pages, rendered from markdown with GitHub-flavoured tables, in the marketing site's own dark-or-light theme. Every article carries the site's real nav and footer, its structured-data entity graph, a table of contents built from its H2s, and a closing CTA banner. External links open in a new tab automatically; internal ones don't.

Also called: blog · articles · guides · resources page

See it
The public blog
CustomerBuildingAmountStatus
Gideon AltHobby Shop$17,730Approved
Ronan Petsch40×64 Shop$12,030Paid
Marlin HooverBarndominium$3,290Approved
Ivy Brubaker40×64 Shop$14,120Open
Ronan PetschHobby Shop$13,550Draft
An article at desktop width: full-bleed hero, sticky contents rail in the left gutter, prose column, closing CTA banner. Sample data — no customer information appears here.
How it works
  1. 1The index lists published posts newest first with hero thumbnails cropped subject-right, date, author and description.
  2. 2An article renders its hero as a full-bleed 25:9 banner capped at the same width as the closing CTA, so the two bookend the text column.
  3. 3H2s are slugged identically on the server and in the renderer, so table-of-contents anchors always match.
  4. 4The theme attribute is stamped on the document before first paint, so a light-mode reader never sees a dark flash.
  5. 5Every marketing page including this one carries the first-party analytics beacon.
Why we built it

The chrome decision is recorded: "The nav and footer are the SITE's own (SiteChrome), not blog-specific ones: the blog used to render a shorter four-link bar while every marketing page rendered Platform / Pricing / Company / Log in, which made the blog feel like a different website (Keith 08-20). One nav, one footer, everywhere." The hero sizing is a fixed bug too: it "used to be a true 100vw band with a height capped at 470px, so on a wide monitor the box kept getting wider while the height stopped — a 2.78:1 banner forced into a 7:1 slot, with object-fit quietly eating most of the composition."

The problem
  • The blog rendered different navigation from the rest of the marketing site.
  • Hero images were cropped to nothing on wide screens.
  • Long articles had no navigation within them.
Sound familiar?
What you get
One nav, one footer, one palette across every marketing page
Heroes render as composed on any screen from a phone up
Readers can jump to a section and see how far through they are
What's inside

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →