Example pages
Landing page
Hero, proof, invitation. The page made almost entirely of blocks — which leaves it exactly one job: deciding their order and what the reader is asked to do.
What it is made of
Every part of this page is documented elsewhere. What is not documented elsewhere is the sequence: a claim, then evidence for it, then the ask. Reordering those is what separates a landing page from a list of sections.
The page
Find out what you can build.
Search any lot. GRIDD reads the planning scheme and answers — with the clause to prove it.
Check any lot
Type an address. The ramp answers with the approval level, not a maybe.
Cited to the clause
Every verdict names the scheme provision it came from — check it yourself.
The full report
A consultant-grade planning report, generated while the map is still settling.
Stop guessing what your block can do.Three free checks. No card, no sales call.
Page-level rules
- Two background tones, never three. The page runs on
--gd-surfaceand stops at the ink band. A third tone reads as a third product. - One ask, repeated — not three competing ones. The hero and the CTA band say the same thing. A page offering a demo, a trial and a call has decided nothing on the reader's behalf.
- The hero carries no raster image. A captured screenshot would be the LCP element and the largest request on a page whose entire premise is instant first paint. The texture is drawn.
- Marketing type is fluid and off the ramp. A display headline uses
clamp()with its own endpoints — the type scale exists for interface text, and the two are different jobs. This is the one sanctioned exception. - Planning colour appears nowhere. The assessment ramp means something on a map; on a marketing page it is decoration wearing a verdict's clothes. Status washes here are grounds for a card, not claims.