// TL;DR
Between March 2022 and January 2023 I stood up three storefronts for my family's trophy business — RS Award, RS Medal, and RS TROPHY — solo, part-time, on WordPress. A fixed four-phase playbook (setup, design, development, launch with SEO and ad tracking) turned each build into a repetition instead of a project. Boring was the point: as a full-time student I needed a stack I could not get stuck in, and I paid for it in skills that did not compound.
January 2023. The first working days of the year went into hosting, a fresh WordPress install, and a commerce plugin stack for rs-trophy.com — the storefront for RUAMSUK PLATING LIMITED PARTNERSHIP, my family's factory in Pathum Thani. The factory has designed and manufactured trophies, medals, and award plaques since 2006, with zinc casting, laser engraving, and metal electroplating done in-house, selling nationwide. This build was the third storefront I had stood up for the business in ten months.
I was not a full-time developer. I was in the second year of a Computer Science degree (Thammasat University) and did the factory’s web work part-time around it (RUAMSUK PLATING LIMITED PARTNERSHIP). That constraint made the stack decision before I did. Solo, part-time, with exams on the calendar, I did not need the most interesting storefront technology. I needed one I could not get stuck in.
//Ten months, three domains
The run started in March 2022 with RS Award, a showcase for plaques and awards. Setup in March. A brand-aligned theme and site structure in April. The catalog, content pages, and CMS workflows in May. Launch in June, with on-page SEO, analytics, and ad tracking wired in before I called it done. RS Medal repeated the same arc from August to November 2022 for the medal catalog: foundation, brand-aligned theme and information architecture, catalog and CMS, then a November go-live with the same tracking checklist.
In January 2023 I broke ground on RS TROPHY. This one was different in kind, not just in product line: the first of the three with real commerce to build — WooCommerce, a cart, a checkout — rather than a catalog that routes buyers to a phone call.
//The playbook that made it repeatable
By the second site I had stopped treating a storefront as a project and started treating it as a recipe. Four phases, roughly a month each, in the same order every time. The third build did not begin with decisions. It began with phase one.
| Phase | RS Award | RS Medal | RS Trophy |
|---|---|---|---|
| Discovery & setup | Mar 2022 | Aug 2022 | Jan 2023 |
| Design — brand-aligned theme | Apr 2022 | Sep 2022 | planned Feb 2023 |
| Development — catalog & CMS | May 2022 | Oct 2022 | planned Mar 2023 |
| Launch — SEO, analytics, ads | Jun 2022 | Nov 2022 | planned Apr 2023 |
Phase one was plumbing: hosting, WordPress, and the plugin stack — which for the trophy site now included WooCommerce. Phase two was design, and I refused to ship a default template: the factory had a real brand, seventeen years old at that point, and the theme had to look like it. Phase three was the catalog itself — products, content pages, and CMS workflows, so that once I handed the site over, edits happened in the admin instead of waiting on me. At the code level every build started the same way too: a child theme, a parent-style enqueue, and a short list of cleanups.
// functions.php — where every one of the three builds started
add_action('wp_enqueue_scripts', function () {
wp_enqueue_style('parent-style', get_template_directory_uri() . '/style.css');
});
// Catalog pages fight for mobile load time — strip what the theme does not need
remove_action('wp_head', 'print_emoji_detection_script', 7);
remove_action('wp_head', 'wp_generator');
add_theme_support('post-thumbnails');
add_image_size('catalog-card', 480, 360, true);Phase four had one rule I refused to bend: a site did not count as launched until on-page SEO, analytics, and ad tracking were live. A catalog nobody can find is a brochure. RS Award went live that way in June 2022, RS Medal in November 2022, and the trophy site would follow the same checklist. Measurement shipping with the site — not after it — was what let the family judge the work by enquiries instead of by my enthusiasm.
<!-- Launch phase, every time: analytics + ad tracking before the site "counts" -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag() { dataLayer.push(arguments); }
gtag('js', new Date());
gtag('config', 'G-XXXXXXX');
</script>//Why boring, and what it cost
The case for WordPress was never that it was good engineering. It was that hosting, theming, cataloging, and — this time — checkout became configuration instead of code. The CMS was the point: after launch, product and content edits did not need a developer in the room. And a stack this common fails in ways a search result has already solved, which matters when your development time is whatever the degree leaves over.
//What the third one changes
RS Award and RS Medal were showcases — catalogs whose job was to get the factory found and start a conversation. The trophy site had a cart and checkout to build and marketing integrations to wire, which made it the same recipe with a much heavier development phase. If the playbook held, design would land in February, the catalog and checkout in March, and launch — SEO, analytics, ads, the usual rule — in April. Ask me in April.
// What I'd Do Differently
- A fixed playbook beat talent I did not have yet. Naming the four phases — setup, design, development, launch — turned the second and third storefronts from projects into repetitions, and repetition was the only way I got faster while studying full-time.
- Boring is a real choice with a real bill. WordPress bought me shipping speed and a CMS the business could run without me, and it charged me in plugin maintenance and in skills that did not compound toward the developer I wanted to become. I would make the same trade again at that capacity — and only at that capacity.
- None of the three builds were the final form. RS Award and RS Medal were later remade in Next.js, and the brands were eventually consolidated onto rs-trophy.com — but the boring versions ran for years and kept the factory visible online while I finished the degree. Shipping the interim thing was the right call.
FAQ
4Q1 //Why choose WordPress and WooCommerce instead of a custom stack for a small manufacturer?
Because the constraint was capacity, not technology. I was a solo part-time developer studying Computer Science full-time, and WordPress turned hosting, theming, cataloging, and checkout into configuration instead of code. A custom stack would have produced a better codebase and a slower business. For a factory that needed to be found and contacted online, shipping in months beat elegance.
Q2 //How long does it take one person to launch a WordPress storefront?
In my case, about four months per site, working part-time: one month each for setup, theme design, catalog development, and launch. RS Award ran March to June 2022 and RS Medal ran August to November 2022 on exactly that cadence. The consistency came from treating the phases as a fixed recipe rather than re-deciding the process every time.
Q3 //What should a small-business storefront launch include beyond the website itself?
My rule was that a site did not count as launched until on-page SEO, analytics, and ad tracking were live. A catalog nobody can find is a brochure. All three storefronts shipped with search optimization and measurement wired in on launch day, so the business could see from day one whether the site was doing anything.
Q4 //Why build three separate storefronts instead of one website?
Each product line — plaques and awards, medals, trophies — had its own brand and its own domain, so each got a focused catalog with its own theme. That matched how the business presented itself at the time, and it kept every build small enough for one part-time developer to finish. Years later the brands were consolidated onto rs-trophy.com, but that is a different chapter.