There were a few reasons why I chose to develop Team Prime in WordPress.
First of all, this is a technology I feel very comfortable with as a developer. I’ve been building custom WordPress themes and providing support on WordPress sites for about six years, since 2013. I can quickly assess what can be achieved with the default WordPress functionality, and what extras we might need.
From the client’s perspective, I believe it’s a fantastic content management system providing they are not left with a large number of options they forget about. Following this principle, I outline the site structure before I start developing the theme. I like to call it development experience, maintaining a clear structure of the project as we go and add features.
Team Prime runs on WordPress 4.9. When I started coding, Gutenberg (WordPress 5.0) hasn’t been released yet. Although the flexibility of updating content was the new website requirement, it wasn’t a priority at that time to have custom page builder and create different designs and experiences. I proposed the use of custom post types supported by the pro version of the Advanced Custom Fields Pro plugin.
I downloaded a base WordPress theme from the Underscores and checked a “_sassify” option to use the SCSS stylesheet language. Why “_s”? It’s a starter theme, how they called it, with functionality reduced to a minimum, but powerful enough to hold additional functions. I am convinced that WordPress sites can perform exceptionally well if the usage of external plugins or fully customizable themes is decreased. Before I start coding, I go through the list of requirements and focus first on the absolutely necessary features, making space for extending the product if needed.
My development environment runs on Local by Flywheel.
I also had a staging environment for Thayer to review my progress hosted on 34SP.