Two locked colors. Twelve signature colors. Each one named, each one assigned a role.
The two-color answer is wrong. The thirty-color answer is wrong. Fourteen is the number where every property can have a fingerprint without the system getting noisy. Bluebonnet and rust are non-negotiable. The other twelve are a pool — each property draws one and only one.
The philosophy
Why fourteen, why theseColor systems fail in two directions. They are either too tight ( two colors only — every property looks identical and the local titles feel impersonal ), or too loose ( use any color you want — the system stops looking like a system after the third property ). The answer is a small, curated, named pool — and a rule that every property picks exactly one. Like a newspaper section getting assigned a color forever.
Locked core.
Bluebonnet and rust. Always present in every property, in fixed roles. The shared bones. You see them and you know this is a Lightbreak property.
Signature pool.
Twelve named colors, drawn from a unified warm-cool spectrum that reads as American local — Texas hill-country to New England coast. Each property gets exactly one.
Neutrals & functional.
Cream paper, four-step ink, hairline rules — these are universal. Functional alerts ( success green, alert rust, info blue ) are universal. Category accents are universal. None of these flex per property.
The locked core
Never replaced · Always presentTwo colors so deeply load-bearing that no property may opt out. Bluebonnet handles every "primary" role: nav, primary CTA, dark sections. Rust handles every "alert" or "featured" role: kickers, the dot in the wordmark, sponsored stripes, the Pro badge.
The signature pool
12 colors · One per propertyA curated palette that walks from Texas warm to New England cool. Every color is named after something a reader could point to. When a new property launches, it picks one of these — and rust returns for alerts. Color names are part of the system: editors say "the Newport Dock blue," not "the navy."
Geographic · Assigned
Pecan
oklch(0.45 0.08 50)
Leander Scoop
Geographic · Assigned
Paprika
oklch(0.52 0.16 28)
Round Rock Scoop
Demographic · Assigned
Clay
oklch(0.55 0.10 38)
WilCo Seniors
Geographic · Unassigned
Wheat
oklch(0.70 0.11 75)
Reserved · Hutto Scoop?
Demographic · Assigned
Forest
oklch(0.36 0.07 150)
WilCo Business Guide
Demographic · Reserved
Sage
oklch(0.62 0.05 145)
WilCo Families
Vertical · Reserved
Moss
oklch(0.48 0.07 130)
Outdoors / Parks vertical
Demographic · Reserved
Plum
oklch(0.40 0.10 320)
New Americans
Geographic · Assigned
Dock
oklch(0.42 0.08 225)
Newport Scoop
Geographic · Assigned
Slate
oklch(0.45 0.04 240)
Rockland Insider
Demographic · Reserved
Saffron
oklch(0.70 0.13 70)
WilCo Young Pros
Vertical · Reserved
Brick
oklch(0.42 0.10 25)
Real Estate vertical
The signature color appears in three controlled places per property: the masthead rule above the wordmark, the kicker above stories ( replacing rust ), and the active-nav indicator. Nowhere else. Body text remains ink. Cream paper remains cream. Rust returns for alerts and the Pro badge.
Round Rock approves $80M jail expansion in 4-to-1 vote
By M. Reyes · 12 min ago
Leander council clears site for new fire station off 183A
By J. Alvarez · 1 hr ago
Lobster boat traffic up 22% as fishing season opens early
By K. Doyle · 4 hr ago
Property assignments
My recommendations · Swap any of themThese are my proposed pairings. I picked them on three criteria: ( 1 ) does the name evoke the place or audience, ( 2 ) does it look right next to the other assigned colors in the system, ( 3 ) is there enough headroom in the palette for future titles. Argue with any of them.
Neutrals — paper, ink, and rule
Never change between propertiesCream paper is the brand. Never plain white at the page level. Never a colored background behind body text. The ink scale is cool-cast — slight blue undertone, never a true black. This is what makes the system feel like an editorial product.
Paper · Cream surfaces
Ink · Text scale
Category accents
Inside every property · For story kickersIndependent of property signature, every story inside every property gets a category. The category color appears only on the small mono cat-tag above the headline. Never on backgrounds. Never on rules. Just the kicker.
Functional palette
Universal · Same across every propertyFor the four signals every interface needs. These are intentionally close to category colors so they sit comfortably alongside, but they are reserved for system messaging.
Do & don't
The mistakes that will break the system fastestWhat makes the system hold together
- Use the signature color in three controlled places only: masthead stripe, kicker above the headline, active-nav indicator.
- Keep page paper cream. Always. Even at the property level.
- Let rust handle every alert and featured role — even on a Newport or Rockland property.
- Name colors by their pool name in conversation. "The Newport Dock blue," not "the dark teal."
- Use the category color only on the cat-tag mono label. Never on a background, never on a rule.
- Use white only as a card surface. The page is cream.
What breaks the system fastest
- Don't put a signature color on a full-bleed background behind body text. That's a brochure, not a newspaper.
- Don't gradient-blend signature colors. The system is flat-color only outside of photo placeholders.
- Don't add a new color to the pool without removing one. Fourteen is the cap.
- Don't give a property two signature colors. Pick one. Pecan or paprika. Not both.
- Don't swap rust for the signature color in alerts. Rust is the alert color across every property.
- Don't introduce dark mode for one property. The brand has no dark mode yet.
- Don't use gold on a cream page. Gold is on-dark only.