Forked from @HugoGiraudel
See the code in action on SassMeister
8674490
// ---- | |
// libsass (v0.7.0) | |
// ---- | |
// Where extends go wrong in libsass | |
// In the following placeholder selector, all the selectors are created as | |
// such using the % syntax | |
%default-parent { |
Forked from @HugoGiraudel
See the code in action on SassMeister
8674490
I admit it, I have a print background. As much as I try to leave that all in the past, it always creeps up and bites me in the ass.
Pixel based image asset management is a mystery to many in print and in the new purely digital world. What constitutes a quality asset file to be reproduced? In print there are clear rules, but in digital display, there are many other variables at play. This post is a description of my journey in finally figuring this out.
With every image, regardless of intended output, it has three primary attributes; pixel width and height, physical width and height, and dpi. Of course there is color space, color profile and a few others, but that is outside the scope of this discussion.
Not sure if you are in the same boat as I, but I could not find any good resource out there that pulled this all together. So here is a step-by-step tutorial for creating a Node.js app from scratch, adding in Grunt and then Node-Sass. Yeah, try and find good docs on Node-Sass alone :(
Hope this is of help!
npm init
- create a clean node project"private": true,
to the package.json
so that your project is not globally distributed as a npm appWeb fonts are pretty much all the rage. Using a CDN for font libraries, like TypeKit or Google Fonts, will be a great solution for many projects. For others, this is not an option. Especially when you are creating a custom icon library for your project.
Rails and the asset pipeline are great tools, but Rails has yet to get caught up in the custom web font craze.
As with all things Rails, there is more then one way to skin this cat. There is the recommended way, and then there are the other ways.
Here I will show how to update your Rails project so that you can use the asset pipeline appropriately and resource your files using the common Rails convention.