Guide
How this page was made.
The build record for the Digimax page: the direction it was chosen from, the tokens, the copy framework cards applied, the compliance rules it was built under, and what the three critique passes found.
Direction
Quiet monument
Chosen from three art directed options. Warm paper ground, one red accent held on a ration, and a single procedural object standing in the hero. The premise mirrors the company: an operator that builds its own tools does not need a page that shouts, it needs a page that stands still and holds up.
The option C hero and method section were extended into the full playbook structure: hero, a thesis, a service index, the numbered method index, the software and its limits, a straight answers section, the company file, and a bookend close that echoes the opening line.
Tokens
Palette, type, spacing
| paper | #FAF7F1 · the ground, never pure white |
|---|---|
| ink | #1C1A17 · headings, hard facts |
| body | #3A3630 · running text |
| dim | #6E675D · labels, captions |
| shade | #ECE7DE · raised cards |
| accent | #C8102E · the single accent |
Accent ration: red appears in exactly five roles, and nowhere else: the kicker mark, the contact rule under both calls to action, the live stage numeral in the method index, the guard rail on the card of things the software may not do, and the live stratum edge on the monument. Focus rings reuse it as a system state, not as decoration.
Type
| display | Archivo, 600 for headings, tracked to about minus three hundredths of an em at display sizes |
|---|---|
| mono | IBM Plex Mono, for labels, the company file, and the numerals cut into the monument |
| script | Mr Dafoe, used exactly once, for the signature at the close |
Spacing is one base unit. Every margin, padding, and gap on both pages is a multiple of it.
Press g on the Digimax page and it shows you its own ruling.
Technique
One source of truth, cut in stone
The hero object is not an image. It is a canvas drawing of a standing four part monument: a cap, four courses of stone, a stepped plinth, a soft ground shadow, and one slow raking light that passes down the face.
The four courses are the four stages of the method. A single array in the page script feeds both the printed method index and the strata of the monument, so the two surfaces can never disagree with each other. Hovering a stage lights its course. Clicking one cuts it in: the numeral goes red on both the list and the stone until it is clicked again, and the cut throws a short burst of stone dust off the face. The dust is stone coloured, never red, so the accent ration survives the flourish.
All motion is gated. Under prefers-reduced-motion the CSS kills every transition and
the script draws the monument once, as a still object, with no animation frame loop at all. The
selection interaction still works, because a discrete repaint is not an animation.
The finish is the cinematic overlay stack: an inline SVG turbulence grain at five percent over a soft vignette, both fixed and pointer transparent.
Words
Copy framework cards applied
All customer facing copy was routed through the worldclass-copy library. The cards that fired, and where each one shows on the page:
| Card | Where it shows |
|---|---|
| headline-seven-techniques | The H1 is built on the uniqueness gate and a unique claim: no agency that rents its dashboard can say "we build the software we run your ads with." The proof and instant gratification properties are deliberately left unused, because no proof asset exists and inventing one is a compliance block. |
| lead-four-functions | The hero paragraph expands the headline rather than switching topic, plants the open loop (it proposes, a person approves, why), raises the temperature, and closes on situational urgency: the un-negated term that is billing you again this week. No deadline, no manufactured scarcity. |
| bullet-point-formula | Every item in the service index carries the three part gate, benefit, curiosity, believability, plus the finishing punch set as its own quiet line. ("Left alone, a losing search term does not expire. It renews.") |
| differentiational-benefit | The mechanism is dramatised rather than listed. The loop is a standing object with the stages cut into it, and the search term report is named as the only page in the account written by the customer rather than by the seller. |
| reason-why-master-key | Two reasons why are stated, never implied: why we build our own tool (the loop is the job), and why the software stops at a person (software that can spend your money without asking is a liability, so ours was built without that power). |
| claim-believability-engineering | Applied as calibration downward. The straight answers section states plainly that there are no case study numbers, no logos, and no claimed results on the page, and why. An admission that seems to unsell is the strongest believability move available to a page with no proof assets to show. |
| dual-readership-path | Skimmers get the H1, the section labels, the bold stems on every service item, the two cards of what the software does and does not do, and the P.S. The P.S. loops back to the headline rather than summarising the page. |
Rules
Compliance posture
- Every fact on the page traces to the research and brief files: Amazon Sponsored Products management for brands selling on Amazon US, the four stage loop, Autopilot and what it is allowed to do, and the company file (registration, representative, office, operating since).
- No invented metrics, client names, case study numbers, team sizes, founding stories, or results. There are none to publish, so none are published. The page persuades on method and on clarity.
- No competitor claims, no superlatives, no badges, no review counts, no guarantees.
- The engine's deterministic claim scanner runs over both pages and must report zero ungrounded tokens before anything can be published.
- Sector firewall: no other client, brand, or company appears anywhere in the markup, the copy, or the comments.
Iteration
The three passes
Both pages were rendered headless at desktop and mobile widths, top to bottom, with the console
watched for errors, then critiqued like a hostile art director and fixed, three times. Each pass
also added one deliberate upgrade, per the house method: the archival marginalia rail in the
first pass, the chisel dust thrown by a cut in the second, and the base unit grid proof, hidden
behind the g key, in the third.
The full log, including what each pass caught and what it added, is in PASSES.md at
the site root.