What Goes Around Comes Around
As a front end developer and designer at Message, I use Mothership to build custom e-commerce websites. I am also part of team Mothership. Basically, I spend my nine-to-five ensuring that the two sides of Mothership feel like a cohesive unit.
While Mothership is fairly new to the open source world, it is being used by quite a few sites, many of which I have developed on the front end. At first, we started each build fresh. While each site was certainly 'bespoke' it also resulted in longer development time from re-writing code from scratch, and lowered the level of consistency between installations. It quickly became clear that we needed a standard to follow, and that standard became our skeleton theme.
Let’s be real: we’re all busy people. In a given day I can be jumping between client projects and Mothership admin design and user experience. We abide by the ethos that Mothership works because we work with it – every day.
We also are constantly evolving and improving upon our craft. Each site developed on Mothership helps to push us a little bit further in our quest to find newer and better solutions for e-commerce.
How do we keep our new client-side developments up-to-date with our tools such as the skeleton theme? Through a process that I tend to just call a “front end audit” but for which I should probably find a catchier name.
It’s simple: as each project wraps up, we go through the site and carefully choose which new developments are the top improvements to be integrated within our skeleton theme. This means that our development is more cyclical than linear.The skeleton theme provides a base for our new builds, where it evolves to support new “real world” innovations, which are then fed back into the theme.
Much like the cycle of evaporation and precipitation that refreshes the world’s water, this process allows us to ensure that Mothership’s front end tools are never stagnant.