The last days i spent a lot of time reading about and getting my head around SVG, which can be kind of complex and sometimes confusing if you’re just starting out. This talk by Sara Soueidan at Beyond Tellerrand helped me a lot to understand some of the basic concepts behind SVG.
Some very interesting insights on what goes into building a huge CSS Framework for an Enterprise Solution like Salesforce.
At Salesforce UX, we are guided by four design principles. In order of importance, they are — clarity, efficiency, consistency, and beauty . These principles assisted us in prioritizing competing goals and helped us make tough calls.
I’d like to share some of the decisions we made while architecting the framework. Some of these choices may be unexpected. And there have been times when our ideas have morphed while building, as we discovered yet another platform or situation we needed to solve for.
Worth a read!
Handpicked code snippets you can use in your web projects. Find web design inspiration with code samples.
A nice collection of Tutorials and Code Snippets from all around the web.
As i wrote before i really liked the concept of “Quantity Queries” in CSS to style elements based on their quantity. It was only a matter of time until someone took the idea to Sass.
Harry Roberts from CSS Wizardry answers a question he got about Atomic CSS and the proper amount of abstraction in your CSS.
That is to say, having
padding: 6px;appear in your CSS 50 times is no big deal. You will feel no performance impact. Gzip will crunch the bejeezus out of it.However, manually typing out
padding: 6px;50 times in your Sass (or LESS, or whatever) is a problem.
Coding Styleguides can help a lot when working with multiple developers on a project, but even if you are a sole dev it can be very useful to write down and keep yourself to some conventions. Hugo Giraudel has put together this very thorough guide specifically targeted on Sass/SCSS Code. Definitely something to bookmark.
A styleguide is not just a pleasing document to read, picturing an ideal state for your code. It is a key document in a project’s life, describing how and why code should be written. It may look like overkill for small projects, but it helps a lot in keeping the codebase clean, scalable and easily maintainable.