This site is a working prototype of the pre-sign-in experience: the full power-transmission portfolio browsable without a login, every claim traced to an official source, and every page built to become an orderable surface the day a customer signs in.
Browse the catalog Try the arrester finderA 16-property benchmark audit found the open-catalog position in grid equipment effectively uncontested: the strongest peers publish polished family brochures but no browsable models, no spec tables in HTML, no part-number search — and searches for our own product designations are won by third-party aggregators and surplus dealers. Meanwhile the e-commerce platform exists but is invisible to anyone without an account. This catalog closes that gap from the public side: it is the marketing face, the search-engine asset, and the shop's front door in one property.
Behind the numbers: content authored by verified extraction from official catalogs and live ERP order data; a three-layer privacy guardrail (a build that fails on customer identifiers, a confidentiality gate that quarantined 10 documents, a pixel-level image audit that caught 16 more); and a build that refuses to pass unless every entry has its page.
Every page ends in a qualified lead: request-information carries the exact family or designation. The finder and search turn "a customer with a nameplate" into an RFQ with an orderable type designation — no phone tag to identify the product.
The long-tail search demand for our model numbers is currently ceded to aggregators. Per-model pages with structured data and readable documentation win it back — and all content is maintained in Payload CMS with an editorial workflow, not in code.
Content provenance is auditable to the source page; customer names, contract numbers and classified documents are blocked by an automated gate with a quarantine trail. The taxonomy is the official GT product hierarchy — one structure from catalog to ERP.
Modular by construction: the same taxonomy handles, the same design tokens, the same content collections everywhere.
Own domain, static, fast, SEO-complete. The marketing site links product sections here; every catalog page links back to campaigns and deep-links "Register / Sign in" toward the shop. No system integration required — this is the work package as scoped.
Payload becomes the single product-content source: the catalog builds from it today (verified byte-identical), and marketing pages can consume the same collections. The daisyUI token theme is the same system targeted for the shop — one visual vocabulary across all three properties.
The e-commerce backend already serves a public catalog with list prices to guests — price is the only gated field. Horizon 3 mounts a small authenticated island on these same PDPs: sign in, and the page you bookmarked gains your price, availability, add-to-quote and your installed base. The URL never changes; the catalog is the shop's logged-out state.
The build is production-shaped today: static output deployable to any host, self-verifying, CMS-ready. The launch checklist is short and mostly decisions rather than engineering — a domain, the request-information routing target, DAM access to replace the staged imagery, and the publication/legal review for which the quarantine evidence is already assembled.