It takes a few seconds to compile, right? Not anymore. You’re reading CSS-Tricks, so you probably write Sass. You can learn more about it from it’s creator here. Autoprefixer is a much better way to handle it. While I’m still a big fan of preprocessors, I’m no longer a fan of using them for prefixing. ![]() Note from Chris: I think Autoprefixer is almost as big of a game changer as CodeKit itself, and they are a perfect match for each other. It’s also totally configurable: just specify which browsers you need to support and it does the rest. It works seamlessly with Less, Sass and Stylus. You just write standard CSS and Autoprefixer adds all the necessary vendor prefixes based on the latest information about each browser. Autoprefixer makes them painless and it’s now built-in to CodeKit. Vendor prefixes: the CSS rules that only an IE6 Engineer could love. Note from Chris: while I haven’t had a chance to use Bower a bunch yet, keeping front end dependencies up to date is the #1 reason I want to. ![]() Update them all with a single click, or pick and choose. It’ll show you the version of each component in your project and what the latest one available online is. Just open the Assets area and choose the Installed tab. CodeKit grabs the latest versions from the web, along with any required dependencies, and puts them right in your project.ĬodeKit also saves you a ton of work when it’s time to update components. Open the Assets area, select the components you want and click the cloud icon. Bower is now built-in to CodeKit, so all those resources are just two clicks away. Bowerīower lets you quickly install over 7,000 components: jQuery, Modernizr, Bootstrap, even WordPress. Meaning designing for interactive states is a lot easier.ĬodeKit 1 could do style injection too, but now CodeKit has it’s own server built-in (which can forward to MAMP or anything else if you prefer) meaning that literally any browser gets the refreshing and style injection. Note from Chris: Not only does the page literally refresh when you change something like a template or JavaScript file, the page will do style injection for CSS changes (whether they came from a preprocessor or not). Once you see this in action, you won’t work without it ever again. Just click the Preview button in CodeKit and then copy the URL to your other devices. ![]() It works even with advanced sites like WordPress and Drupal. Make a change to your code and a split-second later, every device updates to show those changes. CodeKit can do that for you.ĬodeKit will now live-refresh all of these devices and more. That’s a lot of refresh buttons to click. You pull it up on an iPhone, an iPad, a Galaxy S3, Chrome, Firefox and even IE 11 on a PC. Your website has to look good on lots of devices. So instead of listing every new feature, here’s the top four that will make a difference right away: 1. The new version is also 1,400% faster thanks to a bunch of optimizations and works a lot better in team environments.īut what you really care about is how it can make you faster. What’s New in 2.0?įor starters I hired a designer ( Guy Meyer) so the UI no longer looks like it was repeatedly beaten with a DOS 5.1 manual. No JSON files to edit, nothing to install or download. You drop your project folder onto the app and get to work. There are other ways to do these things, but CodeKit’s mission is to take the pain out of the process. All stuff that speeds up both your website and your workflow. It combines, minifies and syntax-checks JavaScript. ![]() It compiles all the cutting-edge languages like Sass, Less, Stylus and CoffeeScript. Bryan is going to introduce it, and I’ll interject here and there to share my thoughts as I’ve been using 2.0 the last month or so.ĬodeKit is an app that helps you build websites faster. Now CodeKit 2.0 it out, which has followed the landscape of front end development, bringing us more powerful tools that are tough to pull off otherwise. In my opinion it changed the game in front end development making it easy to use advanced tools that, while powerful, felt out of reach for many. I’ve been using CodeKit for a couple of years now and I’ve talked about it plenty. The following is a guest post by Bryan Jones, the creator of CodeKit.
0 Comments
Leave a Reply. |