The problem
Survival Life was Native Commerce’s flagship content site, and it served millions of visitors a month. A site at that scale has two jobs at once. It has to publish a steady stream of articles, and it has to turn some of those readers into customers.
Both jobs sat on WordPress. Every new feature had to fit into a site that was already busy, without slowing it down or breaking what readers were using.
What I built
As part of the dev team, I worked on the WordPress build. Together we implemented the site’s blog features and its upsell workflows, the steps that put a follow-on offer in front of a reader who is already buying.
My time at Native Commerce also covered Magento e-commerce work and Selenium QA. The same team looked after a second content property, DIY Projects.
How it works
Content and commerce served the same audience. A reader arrives for an article, and the upsell workflow is what connects that visit to a sale. Both halves had to keep working together, at a traffic level where small breakages get noticed fast.
Selenium was part of how that was checked. Automated browser tests step through a site the way a visitor would, so a regression can be caught before release rather than reported by readers.