SupremeForged

There is no platform underneath this. No WordPress, no headless commerce backend, no site builder. PHP with no framework, a flat-file JSON data layer, vanilla JavaScript, and a hand-built design system. Every page is a real file. Every product URL is real and indexable.

The flat-file decision was deliberate rather than a compromise. Twenty series and a handful of admin users did not justify what a database costs in operational overhead: backups, migrations, hosting requirements. JSON that lives in version control and can be hand-edited in an emergency turned out to be exactly the right amount of infrastructure for the actual problem.

The data model went through one significant migration. Mono and 3-Piece originally shared a single set of fields per wheel, which fell apart the first time a wheel needed genuinely different pricing and photography per configuration. Splitting them into independent sub-objects meant writing a one-time migration tool that could preview the change before committing it. That pattern held for the rest of the build: no destructive data change without a dry run first.

Worth Noting

Visibility runs as a three-step hierarchy rather than a single draft flag. Published, then front page, then featured, each step dependent on the one before it in the data and disabled out of order in the interface rather than validated after the fact.

Wheels available in both configurations cross-link to each other, so nobody researching a Monoblock misses that a 3-Piece exists. Per-size pricing resolves automatically to a starting-from figure, and centre-lock pricing correctly reports a different number on Monoblock pages than elsewhere, pulled from one shared variable rather than hardcoded twice.

Every contact submission is written to a server-side record before the email send is attempted, so an API outage never means a lost enquiry.