WBI Consulting Group Work With Us

Colophon

Typography, stack, and the method.

This site is an exhibit of its own methodology. Its first edition was planned, built, reviewed, and tested by the same five-agent pipeline described in Chapter 03. This edition was rebuilt on WordPress with the studio’s automated WordPress builder.

Pipeline record: how the first edition was built

Our multi-agent framework runs every chapter through five roles. The Planner drafts an ordered ticket list; the Context-Fetcher pulls the catalog quotes each ticket will need; the Feature-Builder writes the code; the Code-Reviewer scores confidence; the Test-Writer runs builds and keyboard-only click-throughs. Below is the actual pipeline record for the first edition’s build.

  1. Planner

    Read the approved plan file, broke the site into six chapter tickets (cover + 5 chapters + index + colophon) and one data-layer ticket.

    Handoff PLAN.json

  2. Context-Fetcher

    Pulled quotes, revenue figures, and product descriptions from TOOL_CATALOG_AND_MARKET_ANALYSIS.md. Flagged the 41-product schema and the four-module platform consolidation.

    Handoff CONTEXT.json (cites §1.1–§10)

  3. Feature-Builder

    Implemented the typed catalog layer (Zod), the FootnoteProvider, the chapter system, the 41 product pages, and this colophon.

    Handoff DIFF.patch

  4. Code-Reviewer

    Verified every footnote maps to a §-reference; checked WCAG 2.2 focus rings, prefers-reduced-motion gates, and semantic <aside>/<dialog> usage.

    Handoff REVIEW.json (score 0.92)

  5. Test-Writer

    Ran pnpm build to confirm every /catalog/[slug] is statically generated; confirmed dev click-through and keyboard-only footnote activation.

    Handoff TESTS.json

Typography

  • Display Literata (400–700)
  • Body Inter (400–700)
  • Mono JetBrains Mono

Literata (Type Together) stands in for GT Sectra / Tiempos at display size; Inter stands in for Neue Haas Grotesk. Substitutes were chosen because they are freely licensed.

Palette

  • Cream #F7F2E8
  • Ink #14181E
  • Oxblood #8C2D19

The stack

  • WordPress CMS Content management and publishing for every chapter and catalog entry.
  • GeneratePress Theme Theme foundation; typography and palette are set once, in the theme.
  • GenerateBlocks Pro Blocks Block layouts and shared Global Styles.
  • SpinupWP Hosting Server provisioning and managed hosting.
  • Hetzner Servers The hardware underneath.
  • Literata, Inter, JetBrains Mono Type The same three families as the first edition.

Architecture: how the content flows

Everything on this site lives in WordPress. Chapters are pages, catalog entries are structured content, and the theme and its Global Styles carry the typography and palette across every template. Content lives in the CMS and its database, not in a markdown blob outside it. The tradeoff is deliberate: every claim stays traceable, and a catalog update is an edit, not a rebuild.

  1. Catalog entries

    Single source of truth. 69 products, each an entry with the same fields: code, title, tier, domain, readiness, utility, capabilities, stack, revenue projections, concept tags, chapter refs.

  2. Chapter pages

    Each chapter is a WordPress page, and catalog listings are queried from the entries rather than typed by hand. Claims in body prose cite the catalog by §-reference in footnotes.

  3. Product detail

    Every product has its own page, rendered by WordPress. Every product is a real HTML document, not a client shell.

  4. SpinupWP

    WordPress runs on a SpinupWP-managed server at Hetzner.

Deployment

WordPress, GeneratePress, and GenerateBlocks Pro, on a SpinupWP-managed server at Hetzner. The cover, every chapter, and all 69 product pages are rendered by WordPress and served as HTML; the catalog lives in the same database as the chapters.

Technical Notes

  • Serial naming: Every product in the catalog carries a WBI-### identifier assigned in order of first appearance in the source document. Client prefixes (present in the internal repository) have been retired from the public-facing catalog. Some archived items retain their internal codenames in body prose where historically useful; none appear in titles or URLs.
  • Fonts: Literata and Inter substitute for the spec’s Tiempos / Neue Haas Grotesk because those are paid families. Literata was chosen over nearer neighbors (Fraunces, Newsreader, Source Serif 4) for its warmer, less-mannered letterforms at poster scale.
  • Blocks: Chapter bodies are built from GenerateBlocks blocks, with footnotes, marginalia, and pull quotes as shared Global Styles.
  • Platform: The first edition ran on Next.js at Vercel; this edition carries the same content, typography, and palette onto WordPress.
  • Catalog source: Every product, platform, technology, and concept on this site is validated against Chapter 02, which is itself sourced to a continuously updated TOOL_CATALOG_AND_MARKET_ANALYSIS.md.

Direct contact

Start a conversation.

Write to us with a paragraph on what you need, and who referred you, if anyone did. We reply within two business days with a scoped proposal or a polite decline. Prose both ways.

hello@wbicg.com → Work With Us