The Era of the go!Theme.

The Era of the go!Theme.

At goBRANDgo!, we are ushering in a new era of web development. We are tired of hacked up themes, broken plugins, and unorganized/inconsistent coding. We are finished with security issues, service tickets, and waiting for long overdue updates from third-party developers. We are moving forward into the future of WordPress development, and the go!Theme and go!Mobile Responsive Framework are taking us there.

The idea of the go!Theme was to create a base theme with our own infrastructure, made from basic CSS, HTML, and Javascript. This way we, start every project with an intimate understanding of the code organization and functionality. This is a huge time saver; whether you’re starting a new dev project or troubleshooting a service ticket, you’ll always know exactly were everything is located. This is very powerful if you are managing hundreds of sites, and was one of the—if not the number one—largest motivators to building the go!Theme.


Since the future of web development is on devices of many shapes and sizes, we built our theme on the custom go!Mobile Responsive Framework.  Although not all of the sites we build are responsive, they are built on the the responsive framework, so they can be converted to responsive in the future without having to recode the structure of the site. This has already been a huge time saver and really takes the sting out of coding sites for multiple devices.

The big breakthough—and probably the most exciting—feature of the go!Theme happened naturally, and sort of by accident. After we had mapped out a couple of different ideas for the basic design of the theme, we realized that there we a lot of inconsistencies among the sites we had been developing, but also a lot of custom features. We knew we couldn’t add everything to one site, so we did the opposite. We thought it would be more valuable to strip the theme down to nothing and the build modules (code snippets) that we could pick and choose from to create any number of unique sites. And any time we have to create something new or custom, we catalog that code and add it to our module arsenal. Not only does this save time, but it allows you to build off the things you already know.

Finally, WordPress is known for having a large number of hacker threats due to how commonly it is used. By building our own theme and using it across all of our sites, we are able to stay up-to-date on all security issues and manage all other updates in a super efficient way.


Enjoying our insights? Enter your email below to subscribe to our monthly newsletter.