Give every acquisition page one operating job

Choose the page’s decision before writing it

A system landing page answers whether an existing foundation fits a buyer’s workflow. A work page shows what was implemented and how far it got. A note isolates one decision, measurement, or failure boundary. A collection page helps somebody choose among those owners.

When one page tries to perform all four jobs, it becomes long without becoming decisive. Repeating summaries across cards adds reading volume but does not create a stronger destination.

Let the homepage route, not inventory

The homepage now promotes four system owners instead of repeating the complete seven-system catalogue. It exposes four recent notes rather than reproducing the entire notes archive, then links to the complete collection where every published note remains visible.

That keeps the first page useful as a route into publishing, directories, data products, and operations while the collection pages retain full coverage for people who need comparison.

Put proof before another promise

Selected cards now show a real renderer or read-only demo capture when one exists. The image links to the same canonical page as the title, and the caption or nearby proof line states the current limit.

Systems without safe public visual evidence remain text-only. Filling every empty card with unrelated art would make the catalogue more decorative and less trustworthy.

Keep crawl signals and outcomes separate

Every indexable route retains a self-canonical, an index directive, a current release or note date, and direct internal links from its owning collection. The release checklist also requires an edge purge and a fresh-session verification so changed hub HTML is not judged through an old cached tab.

Those controls make the release coherent and discoverable. They do not establish that a search engine recrawled the URL, changed its snippet, indexed the page, ranked it, or sent useful traffic.

Measure the next decision

The useful measurement is not “a page exists.” It is which route was discovered, which page received a qualified visit, which system or proof path was opened, and whether the visitor reached the existing contact workflow.

The site already records cookieless traffic and explicit contact-CTA events. A later acquisition conclusion still requires observed data; this release does not manufacture one from the page redesign.

What the implementation proves

• Four featured systems selected for the homepage and all seven retained in the systems catalogue
• Four recent notes selected for the homepage and every published note retained on the notes collection
• System, work, and note routes connected through direct canonical-owner links
• Self-canonical, index directive, release last-modified, and contact-event contracts retained