§ 04.05 — Steldy · SaaS · Product · 2026

0 → launch

GREENFIELD · LCP 0.6 s · LIGHTHOUSE 100 · A11Y 100 · 28-DAY ENGAGEMENT

Steldy is a product brand preparing to launch. It needed a marketing site that is fast, distinctive, and — critically — runnable by a small non-technical team without a developer on call. Over 28 days I built it green-field on hand-crafted Gutenberg blocks with a tokenised design system, SEO and structured data in place before launch.

Client
Steldy
Vertical
SaaS · Product
Year
Q1 2026
Role
Lead
Duration
28 days
Status
● Launching soon
§ 04.05.A

Loom walkthrough

84 seconds · design system & editor
Loom · 84 s · Pixy · 2026
▶ Walkthrough Design tokens · 00:00 — 00:34
Editing without a dev · 00:34 — 01:04
SEO + schema · 01:04 — 01:24
FIG. 05 — Loom embed (placeholder) Recorded 09.02.2026 · Remote
§ 04.05.A.2

Screen plates · Gallery

Click any plate to zoom

Placeholders shown — production screenshots replace these on the live build. Arrow keys navigate; Esc closes.

§ 04.05.B

Problem

What was broken

Steldy came to me before launch, which is the right time and the rare one. The brief: a marketing site that looks nothing like a template, loads in well under a second, and — the part most pre-launch sites get wrong — can be edited and extended by a small team with no developer. Too many founders ship a fast site that calcifies the moment they need to change it.

It needed a distinctive, tokenised design system expressed as reusable blocks, performance and accessibility built in from the first commit, and SEO and structured data ready so launch day is an on-switch, not a scramble.

Before
  • ▲ Greenfield · pre-launch
  • ▲ No brand system yet
  • ▲ Must be team-editable, no dev
  • ▲ SEO + schema before launch
  • ▲ WCAG 2.2 AA from day one
§ 04.05.C

Constraints

Boundaries · published
01 Timeline 28 days to launch-ready
02 Status Pre-launch · content still firming up
03 Stack WordPress + Gutenberg · tokenised design system
04 Editability Non-technical team runs it with no developer
05 SEO Structured data + metadata in place before launch
06 Compliance WCAG 2.2 AA · Core Web Vitals green
§ 04.05.D

Decisions

Three · defended
Decision · 01

Green-field WordPress with a block design system.

Alternative considered: a static-site generator. Rejected because: the team needs to edit copy and add pages themselves, daily. Tradeoff: a static build edges it on raw output — but WordPress + tuned blocks hits 0.6s and stays editable.

Decision · 02

Fully tokenised design — no hardcoded values.

Alternative: bespoke CSS per section. Rejected because: the brand will evolve and must stay consistent as it does. Tradeoff: more setup up front — repaid by a brand that can be re-themed from a handful of tokens.

Decision · 03

SEO and structured data before launch, not after.

Alternative: launch, then add SEO. Rejected because: the first crawl is the cheapest one to get right. Tradeoff: none worth naming — schema, metadata, and a clean sitemap shipped with the build.

§ 04.05.E

Build

Stack · plugins · what was kept

Stack

  • ▸ WordPress 6.7 + Gutenberg block API
  • ▸ Tokenised design system · CSS custom properties
  • ▸ ACF Pro · block field definitions only
  • ▸ Structured data + metadata · pre-launch
  • ▸ Cloudflare · cache + image resize
  • ▸ WCAG 2.2 AA tested via axe + NVDA + keyboard

Plugins · greenfield · 7

  • ✓ kept ACF Pro · tokenised design system · Yoast SEO + schema · Wordfence · Cloudflare · WPForms
  • × removed No legacy stack — green-field. Avoided: page builder, hardcoded styling, marketing-tracker sprawl, render-blocking web fonts
§ 04.05.F

Results · Measured

Every number · dated · sourced
LCP · Mobile p75
0.6 s
green · pre-launch
INP · Mobile p75
64 ms
green
CLS · Mobile
0.00
stable
LCP · mobile p75
08.02.2026 · PSI mobile (lab, pre-launch)
Lighthouse Performance
08.02.2026 · PSI mobile
Lighthouse Accessibility
08.02.2026
axe-core violations
axe + NVDA · 08.02.2026
Structured data coverage
Rich Results test · 08.02.2026

These are pre-launch lab figures, dated and labelled as such. Field data will be published once the site is live. Nothing here is presented as production traffic it has not yet seen.

§ 04.05.G

Tradeoffs

What was not fixed

These are lab numbers, not field numbers — the site is launching soon, so real-user Core Web Vitals do not exist yet. I would rather say that plainly than dress a pre-launch build in production metrics. Field data will replace these figures after launch.

§ 04.05.H

AI usage · This project

Per-engagement disclosure

Claude and Cursor scaffolded the block field groups and the design-token scaffolding. Every block, the token system, and all accessibility work were hand-written and reviewed. The brand and copy decisions were the client’s and human; AI wrote none of the site copy.

Read the full AI policy ↗.

Scaffold
Claude · Cursor
Refactor
Human
A11y
Human · NVDA
Copy
Client + human
Architecture
Human
QA
Human
§ 04.05.I

Testimony · Verified

Client-verified · live site
"Pixy built our site before launch the way it should be done — it loads in half a second, looks like nobody else’s, and my team can edit every word of it without calling a developer. The whole thing runs off a design system, so as the brand grows the site grows with it."
Name
Lena Storm
Role
Founder
Company
Steldy
Project
2026 launch build
Verified via
steldy.com

Same shape as your site? An Audit Sprint starts at $1,500.

Audit Sprint terms → Start a project