zulooorder.blogg.se

1. #Indented sass codekit for mac
2. #Indented sass codekit install
3. #Indented sass codekit update
4. #Indented sass codekit professional

I write a lot of CSS (SCSS) and a decent amount of JS.

#Indented sass codekit professional

It's intriguing though, and I can definitely see that these kinds of tools in a professional workflow would be awesome. I've started looking into this rework and gulp approach, and ran into some brick walls today with gulp (especially re: gulp.watch()).

#Indented sass codekit update

The toolkit's very recent update left behind the traditional sass build approach for Rework, based on Gulp. In this same way I have some rules that quickly produce my own html & css boilerplates.ĭigging into Basscss got me deeper into sass and experimenting with OOCSS. On top of default Emmet, when parts of a project allow for it (repetition of certain markup), I configure a shortcut in emmet's snippets.json file to spit out html with a keyword. I've been learning both more, and trying out Prose.io for the multi-author support. Jekyll + GitHub Pages is really an awesome resource. I used codekit for a while, but once I got knee deep in jekyll I used it less. I use sublime 2, iterm, duckduckgo, google, and youtube. Also allows me to tweak the designs extremely quickly as it's still just a local static site - no waiting around for local servers loading or anything like that. This is great for clients, who get to see what the site will look like, without having to do any backend at all until the design has been signed off. I use Photoshop for image editing or graphics creation, not for designing websites.Ĭreate a fully clickable static demo of the finished project. One SASS file imports all other partial SASS files (layout/ home.sass, partial/nav.sass, and so on).ĭesign everything in-browser. Approach/Workflow/"Rules"įor every new project I'm using my own boilerplate/bootstrap HTML/CSS base setup that has been refined for years, based on experience. Millions of plugins and good documentation is key for "beginners".Īngular Just recently started getting into Angular as we needed a good middleman/bridge solution at work. JQuery I'm not very good at JS, so jQuery is my choice. Reason is the same as for HAML: I find the SASS syntax quick to use, and I'm a big fan of indentation logic. Reason: I find the HAML syntax extremely fast and easy to work with. I use it to create Wordpress themes, anything.

HAML I do all my HTML in HAML, even if it's not a Ruby project.

#Indented sass codekit for mac

GitHub for Mac As a designer I love visual interaction, so I prefer using the GUI client of GitHub instead of doing through Terminal.

Google Chrome Safari is faster for me in day-to-day surfing and personal stuff, but Google Chrome feels snappier in development. I love Atom but it's not as smooth as ST. Sublime Text 3 / Atom Still flip-flopping between these two. Also to run a live local server that I can access from any device on my network.

#Indented sass codekit install

Install a few extra packages to help you speed up your workflow like: Derby (for Bourbon/Neat) and Sidebar Enhancements.Ĭodekit For auto-compiling my SASS and HAML files down to CSS and HTML. I highly recommend them in place of any other grid system like Bootstrap/Foundation, because they keep your HTML extremely clean and flexible. These Sass extensions by Thoughtbot (extra mixins, grid system, and basic styles) help me organize the basic things so that I can focus on implementing the design into code. That way, my html docs only need to reference the one compiled 'all.css'. CodeKit recognizes the in all.scss, and only compiles all.scss. Personally, I have a main Sass file (all.scss) that uses to reference the other Sass files in my project (broken up by page).