Skip to content
Portfolio/Capabilities

CAPABILITY 08 / 30

Web pages, assembled not designed

A shippable page in minutes, from approved sections, with the accessibility numbers measured.

IN PRODUCTION

This runs in client systems today. The sample below was regenerated for a fictional company.

The same system that writes documents builds web pages. A page is assembled from an approved section library rather than designed from scratch, and then measured: heading order, contrast, tap targets, weight, and whether anything loads from somewhere else. The result is a page that is on brand because it could not have been anything else.

TRY IT / RUNS IN YOUR BROWSER

Use it here.

The mechanism is the production one. The company, the catalogue, and every figure are fictional.

Loading the page system.

THE OUTPUT / GENERATED FOR APEX INSTRUMENTS

What comes out.

HTML
Meridian Pro landing pageScreen · 1 page · A complete self-contained page: hero, three value blocks, specification table, partner quote, plan comparison, questions, and a contact block whose form is marked as a demonstration and has no endpoint.Open ↗
JSON
The approved section libraryData · Fourteen sections with what each is for, the slots it exposes, and the rules that get a section refused. Nine of them are on the sample page.Open the file ↗
JSON
Quality report, measuredData · The output of measure.mjs driving the page in Chromium at three widths. Every figure in it was measured, none was asserted by hand.Open the file ↗
MJS
The quality measurement, as codeData · Runs the eight checks against the page and writes data/quality.json. Exits non-zero if any check fails.Open the file ↗

THE MECHANISM / SHOW THE SHAPE, NOT THE SOURCE

How it works.

What a skill is
  1. 01Assemble

    Sections are chosen from the library, in an order the library allows.

  2. 02Fill

    Content goes into defined slots, with the same slot rules as every other output.

  3. 03Style

    Tokens do the styling. No page introduces a new value.

  4. 04Measure

    Heading order, alt text, contrast, tap targets, weight, and external requests are measured on the built page.

  5. 05Publish

    The page ships as one self-contained file with nothing loading from elsewhere.

WHAT IT READS

  • The approved section library and its slots
  • The page content
  • The measurable quality floor

WHAT IT CHECKS BEFORE IT SHIPS

  • Headings run in order with no level skipped
  • Body and accent contrast pass on their own grounds
  • Tap targets at least 44 pixels
  • No external request beyond the font stylesheet
In production: partner microsites and landing pages built from one section library, with the same checks that gate the documents.

The mechanism runs inside client systems. Everything on this page was regenerated for Apex Instruments, a company that does not exist. Client names, source files, and internal wording stay private.

What it producesWhat is being built next