{"id":194,"date":"2015-06-18T08:50:47","date_gmt":"2015-06-18T15:50:47","guid":{"rendered":"https:\/\/traverstodd.com\/?p=194"},"modified":"2015-06-24T14:33:21","modified_gmt":"2015-06-24T21:33:21","slug":"creating-a-base-development-theme","status":"publish","type":"post","link":"https:\/\/traverstodd.com\/creating-a-base-development-theme\/","title":{"rendered":"Creating a Base Development Theme"},"content":{"rendered":"
When I first started working with WordPress, I often started with very basic themes and hacked away at them to clear all of the unwanted code.\u00a0 I started recognizing which parts were important to my workflow, and which parts I could do without.\u00a0 I don’t know about you, but I often start my development with some basic components and use common classes and ids across sites.<\/p>\n
Eventually, I took all of those elements and common styles and created a very basic, mostly style-free base theme.\u00a0 I use this theme as a starting point for all WordPress development.\u00a0 So when I’m handed a Photoshop document with a design, I don’t have to waste time creating basic HTML structure and styles.<\/p>\n
As the years went by, the theme has evolved.\u00a0 For instance, my colleague often gives me a snippet of code to add to functions.php to stop some unwanted default WordPress behavior.\u00a0 I add that code to the development theme so it is ready for me when I start building out another site.\u00a0 As your coding experience progresses and the trends of modern web design change, your theme will evolve with it.\u00a0 <\/p>\n
If you find\u00a0 yourself using Font Awesome<\/a> icon fonts, why not put a link to the CDN in header.php?\u00a0 If you often use custom post types, add that to your functions.php file and comment out until needed.\u00a0 These are things that I use often, but if I don’t t need them, it’s so easy just to delete them.<\/p>\n