background preloader

Home · stubbornella/oocss Wiki

Home · stubbornella/oocss Wiki
Object Oriented CSS How do you scale CSS for thousands of pages? Object Oriented CSS is an answer. It’s an approach for writing CSS that’s fast, maintainable, and standards-based. It adds much needed predictability to CSS so that even beginners can participate in writing beautiful websites. Nicole Sullivan first presented it at Web Directions North in Denver and the response has been overwhelming.

Related:  CSSHTML / CSS / JSdesignUXCSS Architecture

How To Create A Custom Preloading Screen Are you building a one page parallax scrolling website and getting concerned about your page load time? Lets be honest, the one page websites can get quite bulky very quickly even when you optimize everything. Related Screencast Getting started with Grunt and Sass - Ryan Christiani - Front-End Developer - Ryan Christiani – Front-End Developer There are a lot of new tools out there to help speed up and streamline your workflow as a developer, and to be honest they can seem a bit daunting to get into. Two new tools I have started using this year were Grunt and Sass. Grunt is a commandline JavaScript Task Runner, and Sass is a Css preprocessor that lets you write more powerful css, with the use of variables, mixins/functions and nesting! Lets take a look at getting started using Grunt to compile our Sass. If you are new to the working in the command line, check my quick overview of some of the basic commands to help get you started.

MindBEMding – getting your head ’round BEM syntax One of the questions I get asked most frequently is what do -- and __ mean in your classes? The answer is thanks to BEM and Nicolas Gallagher… BEM – meaning block, element, modifier – is a front-end naming methodology thought up by the guys at Yandex. More Transparent UI Code with Namespaces When we work at scale, we often find that we spend a large amount of our time reading, maintaining, and refactoring existing code, rather than writing and adding new features. This is the reason we focus so much on things like architectures, naming conventions, methodologies, preprocessors, scalability, etc.: because writing CSS is easy; looking after it is not. What we want is to be able to write code that is as transparent and self-documenting as possible. Transparency means that it is clear and obvious (to others) in its intent; self-documenting means that we don’t have to lose time to writing and reading lengthy, supplementary documentation.

20 Impressive CSS3 Techniques, Libraries and Examples Danny Markov In this list we’ve gathered for you some of the best sources of CSS goodness. We’ve chosen some amazing demos from various artists that come to prove that nowadays everything is possible with CSS. We’ve also included articles that depict the awesome new features of CSS3 and a few helpful libraries full of CSS tricks. Toolkit — Susy 2.2.12 documentation The Susy 2.0 toolkit is built around our shorthand syntax. Use the shorthand to control every detail, and adjust your defaults on-the-fly, so you are never tied down to just one grid, or just one output style. Span [mixin]¶ Naming CSS Stuff Is Really Hard This isn't quite a post about CSS architecture. This isn't really a post about naming conventions, either. Instead, let's talk about what we're calling elements. The names themselves. The things we use to link blocks of styles to the elements they're associated with. 9 out of 10 developers agree: naming things is by far the most difficult part of writing CSS.

CSS Zen Garden: The Beauty of CSS Design So What is This About? There is a continuing need to show the power of CSS. The Zen Garden aims to excite, inspire, and encourage participation. To begin, view some of the existing designs in the list. 24 JavaScript Best Practices for Beginners As a follow-up to "30 HTML and CSS Best Practices", this week, we'll review JavaScript! Once you've reviewed the list, be sure to let us know what little tips you've come across! JavaScript utilizes two different kinds of equality operators: === | !== and == | != It is considered best practice to always use the former set when comparing.