Dealer Storefronts

At Revnix I work on the frontend of dealer storefronts running on the company's Nextly CMS — a TypeScript-native, open-source CMS for Next.js. Three brands run this stack today: 21st Century Equipment (25+ locations across CO/WY/NE), 4Rivers Equipment (CO/NM/TX), and The Backyard, 21st Century's home & ranch brand.

Dealer sites look like marketing sites but behave like products: deep inventory, parts and service flows; editorial teams publishing daily; and enterprise realities — consent management, tag managers, CRM integrations — that have to coexist with performance budgets.

• CMS-driven page systems — layouts and blocks that editors compose without engineering involvement, on Nextly schemas.
• Commerce flows — auth, role-based access and Stripe payment paths that work across brands.
• Performance as a requirement — Lighthouse 90+ budgets on real content-heavy pages; Core Web Vitals monitored, not hoped for.
• Trust & compliance — CSP hardening, Osano cookie consent, GTM and Dynamics 365 integrations that don't fight the page.
• Internal tooling — admin interfaces that keep content and operations teams unblocked.

Production dealer work rewires how you think about frontend. Component systems have to survive editors, not just designers. Every integration is a performance tax negotiation. And a CSP violation or a consent banner misfire on a US-facing brand costs more than any bug I've shipped in a side project. It's the best possible school for caring about the details nobody notices until they're wrong.

• Three live brands, 25+ locations, daily publishing — on a stack I help maintain.
• Performance and quality budgets that hold on production traffic.
• The INP and App Router notes in my writing come from these sites, not theory.