When we’re the client (we have a new appreciation)
Makers and doers, making and doing
Yes, we could have just used a WordPress template, but there are some really good reasons we chose not to. With WordPress, retrieval goes like this: request, pull it from the database, the server compiles the information, and then sends it back to the user requesting said information. This isn’t particularly fast. Also, using a template just isn’t our style—we’re Makers and Doers, not Eh, This Seems Good Enough-ers.
With our approach, files are ready to go and stored on a CDN (Content Delivery Network), meaning the file doesn’t have to go through a database. So unlike a WordPress template, our site requests don’t have to communicate with a database, there’s no parsing of templates, no buildout markup, no generation of html and sending it to the client getting in the way of delivering content to you, the user, who we’d love to do business with.
What it all means and why that matters to you
Basically, we have the expertise to leave “off the shelf” WordPress templates in the dust. Getting a user/customer to your site is only half the battle—if load times are slow or if the user experience is clunky in any way, users will often ditch the site in seconds. That’s a big problem, particularly for e-commerce businesses.
Our custom builds deliver dramatically superior UX, are easy to maintain, and far more flexible than WordPress template sites. These advantages add up to lower long-term costs and higher conversion rates. We think that’s a pretty terrific outcome. But for now, we’re going to go back to being makers and doers, and leave the clienting to our clients.