![]() I’ve configured CodeKit to use it’s internal LESS compiler, to minify the file, and to run Bless on the file once it has been compiled: Obviously, I use LESS but I’m not one to take a strong stance on why you should use it (or why you shouldn’t use Sass). This means that when I enqueue and register stylesheets and JavaScript, I use the files that are located in the root of their respective directories – not what’s located in the working subdirectories.Īgain, all of the files in the root of these directories are generated and output by CodeKit. Similarly, all of my JavaScript is written in the dev directory – CodeKit combines, minifies and outputs the final version of the files into the root of the js directory. ![]() Any stylesheet that resides in the root of the css directory is generated by CodeKit. Obviously, I use LESS to write CSS, but the less directory serves as my working directory. Within the css directory, I have a less directory and within the js directory, I have a dev directory. In the screenshot above, you’ll notice that I maintain separate directories for CSS and for JavaScript. Though there’s no single “right way” to configure it, here’s how I’ve been using CodeKit for WordPress plugin development.īefore dropping my project into CodeKit, I start with a boilerplate directory structure: ![]() It has support for LESS, Sass, a couple of JavaScript linting utilities, dependency management, minification, and so on. The thing is, there’s a variety of ways to tailor CodeKit for your needs. In the post, I briefly touched on CodeKit, but I didn’t really talk about why I use it nor did I share how I configure it for my WordPress-based projects.ĬodeKit is a platform-agnostic application – it’s meant for anyone who is doing web development – and it has been one of the single best tools that I’ve added to my WordPress toolbox in the past year. Sure, but you have to admit that may not matter to some people.Earlier this week, I shared my approach to and the tools used for building a WordPress Plugin. I prefer a build folder with the result.įinally, having the build process rely on both a Mac and having Codekit installed isn't going to win you any goodwill. That’s a fair point and after playing with CodeKit a bit, I definitely have some issues with the way it builds - I don’t like the optimised and converted files sitting next to the source files. I realized that if I had just invested a bit of time learning even one build tool I would have saved myself a lot of time trying to get someone else's view of how my project should be organized to match my own vision. Would you prefer your software was a subscription? That would solve the issue you’re talking about, but is worse (in my opinion) for other reasons. I think the onus is on the purchaser when it comes to buying software late in the product cycle. If you bought it late in the cycle, you should have known that a major update could be coming soon. You received an app that did what it said on the tin. My issue was that is did buy Codekit 1 and was burned. The code you need for CodeKit is pretty much the same as the code you need without it. That’s not a fair comparison - CodeKit works with all the stuff you’d likely use with or without it: HTML, Sass, Markdown etc. That doesn't mean I end up knowing or understanding the code that Dreamweaver creates. When you are able to share that you know (make / grunt / rake / etc) during an interview, you are going to be in a better position, and again, increase your dollar worth. Mostly, I realized that if I had just invested a bit of time learning even one build tool I would have saved myself a lot of time trying to get someone else's view of how my project should be organized to match my own vision.įinally, having the build process rely on both a Mac and having Codekit installed isn't going to win you any goodwill. ![]() I have zero issue with paying for software, especially when it saves me time. I would learn more and become better at my profession therefore, becoming worth more therefore, increasing my hourly value by investing in myself and not a fancy app. Sure, Dreamweaver might do some fun stuff, and I might even end up being the best at Dreamweaver but that doesn't mean I end up knowing or understanding the code that Dreamweaver creates. An investment in Codekit would be like me investing in Dreamweaver. What value do you place on 2 hours of your time? Grunt is awesome, but that doesn't mean CodeKit isn't awesome.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |