02Frontend EngineerOct 2026Remote · Lagos, Nigeria
ThatPurpleDot
Custom WooCommerce storefront
- Product
- Three-brand fashion storefront
- Build
- Custom theme and commerce plugin
- My focus
- Architecture, shipping, brand rules, accessibility and tests
- Status
- Live
- Stack
- WordPress
- WooCommerce
- PHP
- TypeScript
- Vite
- Tailwind CSS 4
The product
That Purple Dot is a fashion house with a ready-to-wear line, a second label and a bespoke atelier. All three sell through one WooCommerce store with a shared bag and checkout, but each needs its own catalogue, landing page and rules.
I built it as a custom theme and a custom plugin, using TypeScript modules and Tailwind on the front end and no page builder. The store is live at thatpurpledot.com.
My role
This is my own build, from architecture to tests. I made the design decisions and recorded them as written decision notes in the repository.
Theme and plugin, kept apart
One rule for where code goes
If something has to survive a redesign, it does not belong in the theme. The theme holds templates, styles and interface modules; the plugin holds brands, collections, catalogue rules, shipping, policies and the newsletter, and never depends on the theme.
Filters as the contract
Templates ask the plugin for what they need through named WordPress filters, for example the active brand, the homepage content or a product page's data, and get back validated, normalised data. Templates never work out brand or collection relationships themselves.
A small build pipeline
TypeScript modules and Tailwind are built with Vite and loaded through its manifest, with self-hosted fonts and design tokens in one place.
Deterministic shipping
Delivery pricing is a pure function: the same bag and address always give the same answer, and it can be tested without WordPress running.
Three kinds of destination
Lagos is priced by delivery area at a fixed rate. Other Nigerian states use a regional base rate up to two kilograms, then a rate for each started kilogram above that. International orders use the first weight row at or above the bag's weight for the destination zone.
It says why when it cannot quote
Each case where no rate is offered has a named reason, such as a product with no weight, no area selected or a bag over the maximum weight, and each reason maps to a customer message the merchant can edit. An unset fallback rate means no delivery, never free delivery.
Edge cases found along the way
Weights are rounded to remove floating-point noise, so 1.1 kg plus 1.9 kg is not charged as a fourth kilogram. The Lagos area field checks country and state together, because Louisiana shares the code LA. A saved Lagos area is ignored for any other state.
Orders keep their own record
Each order stores the shipping calculation it was charged with, so later rate changes never alter past orders. The merchant manages rates in four sections that save independently and reject the whole section if any value is invalid.
Brand constraints
Brands as a first-class concept
Brands are a plugin-owned taxonomy with stable slugs. Two brands can be assigned to products; the atelier's work is a separate content type and cannot be purchased.
Every way of editing is covered
The brand rule is checked in the full product editor before anything saves, in quick edit and bulk edit, and on writes through the WordPress REST API, so a product cannot pick up an invalid brand from a side door.
Collections belong to one brand
Each collection has exactly one owning brand, which cannot change while the collection has products. Catalogue pages are scoped by brand and collection, and breadcrumbs are built from them, not from generic categories.
Accessible interface and browser tests
Dialogs on the native element
Modals use the native dialog element for focus trapping and Escape. Focus returns to the control that opened the dialog, a drag that starts inside does not close it, and the close animation is skipped for people who prefer reduced motion.
Menus and accordions
The mega menu is a disclosure with proper expanded state and keyboard support, and opens on hover only for mouse users. Mobile submenus move focus predictably. FAQs use native details elements linked to the URL.
Motion that can be turned off
The video hero does not autoplay under reduced motion and has a labelled play and pause control; carousels and transitions follow the same setting.
Tests without a test framework
Integration scripts run against a real local WordPress install, create their own fixtures and clean up after themselves. Browser tests launch headless Chrome and drive it directly over the Chrome DevTools Protocol to check viewports, keyboard navigation and the real checkout. Small unit tests cover the interface modules.