The Objective
Build a scalable public experience for utility, telecom and underground equipment, then give the owner direct control of the catalog and website through TCG OS rather than developer-only edits.
R6 // CASE STUDY 002
THE CONNER
GROUP.
The catalog became a system. A public equipment experience backed by TCG OS so categories, equipment, imagery, content and publishing could be managed without rebuilding pages by hand.
THE MISSION
SELL THE EQUIPMENT.
CONTROL THE PLATFORM.
The objective was to modernize the customer-facing equipment experience while creating a backend that could own the content, navigation, equipment, media and website governance behind it.
The Starting Point
A product-heavy equipment website changes constantly. The architecture had to support those changes instead of fighting them.
01Equipment categories and models needed structured management rather than hard-coded pages.
02Media had to be reusable, assignable and manageable from one place.
03Public navigation and category visibility had to follow what actually existed in TCG OS.
04The website-management platform had to stay separate from the company’s telephone-based sales process.
THE ARCHITECTURE
CONTENT IN TCG OS.
EXPERIENCE ON THE WEB.
The public site renders the experience. TCG OS owns the structured content behind it - from navigation and equipment to media, SEO and publishing.
TCG OSWEBSITE CONTROL
THE BUILD
FROM EQUIPMENT PAGES
TO A CONTENT ENGINE.
The build moved vertically: establish TCG OS, prove equipment and media management, then let the public website render the structured content.
Equipment-First Website
A modern equipment-focused site with clear categories, industries, service and company content.
Website Command Center
A backend platform to manage content, equipment, imagery, publishing and site governance.
Structured Catalog
Categories, manufacturers, models, specifications, galleries, featured items and publishing state.
Reusable Media Operations
Media assignment, category imagery, primary images and supporting documents were managed as website assets.
R6 // TCG DEPLOYMENT RECORD
PHASE 01 // PUBLIC EXPERIENCE
Equipment-First Website
The public experience was designed around the equipment customers are trying to find and the work they need to perform.
PROBLEMS SOLVED
THE DETAILS
HAD TO HOLD.
The difficult work was not the hero. It was getting a dynamic equipment platform to behave correctly as categories, products and media changed.
Problem: Empty or unbuilt areas should never appear on the public site.
Change: Public navigation and homepage equipment areas were wired to the records actually created and published.
Outcome: The site reflects the catalog instead of exposing placeholders.
Change: Public navigation and homepage equipment areas were wired to the records actually created and published.
Outcome: The site reflects the catalog instead of exposing placeholders.
Problem: Product creation, duplicate slugs and record identifiers created edge cases during catalog management.
Change: Create/update logic and uniqueness handling were hardened around the equipment model.
Outcome: Catalog entries could be created and maintained reliably.
Change: Create/update logic and uniqueness handling were hardened around the equipment model.
Outcome: Catalog entries could be created and maintained reliably.
Problem: Primary imagery, gallery images and file paths had to stay consistent across admin and public views.
Change: Media assignment and primary-image behavior were tied into TCG OS.
Outcome: Equipment visuals became a managed part of the content system.
Change: Media assignment and primary-image behavior were tied into TCG OS.
Outcome: Equipment visuals became a managed part of the content system.
Problem: A website platform can easily drift into becoming an accidental CRM.
Change: The durable architecture explicitly kept customer transactions and sales activity outside the website-management core.
Outcome: TCG OS stays focused on controlling the public digital asset.
Change: The durable architecture explicitly kept customer transactions and sales activity outside the website-management core.
Outcome: TCG OS stays focused on controlling the public digital asset.
SYSTEMS DEPLOYED
THE WEBSITE
HAS A BACKBONE.
The result is a public equipment website with a structured management platform behind it.
Public Website
Equipment, industries, service, media and company experience.
TCG OS
Website command center for the public digital platform.
Equipment Center
Categories, manufacturers, models, specs and display information.
Media Library
Reusable images, documents, galleries and asset organization.
Navigation Manager
Structured menus and published website organization.
SEO Foundation
Metadata, canonicals, redirects, schema and sitemap controls.
Admin + Audit
Users, roles, sessions, settings and audit history.
SQL Content Model
Structured system of record powering the website.
TWO SIDES OF THE SYSTEM
WHAT CUSTOMERS SEE.
WHAT TCG CONTROLS.
Switch between the customer-facing equipment experience and the command center that manages the website behind it.
Scope note: TCG OS is presented here as a website-management platform. It is not positioned as the company's sales-order, rental-contract or billing system.
THE RESULT
THE WEBSITE SHOWS THE EQUIPMENT.
TCG OS CONTROLS THE MACHINE.
Structured Ownership
The public catalog is backed by managed equipment and content records.
Owner Control
Website updates can be made through TCG OS instead of recurring code edits.
Room To Grow
The platform can expand with new categories, equipment, media and content.