# The Future of OOCSS: A Proposal

DevFeed: [The Future of OOCSS: A Proposal](<https://devfeed.tech/articles/the-future-of-oocss-a-proposal-29528.md>)

Original publisher: [Read original article](<https://philipwalton.com/articles/the-future-of-oocss-a-proposal/>)

Published: 2013-01-17T19:02:16Z

Content type: article

Language: en

Sources: [Philip Walton](<https://devfeed.tech/sources/philip-walton.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Sass](<https://devfeed.tech/topics/sass.md>), [ui](<https://devfeed.tech/topics/ui.md>)

Tags: [css](<https://devfeed.tech/tags/css.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [sass](<https://devfeed.tech/tags/sass.md>), [ui](<https://devfeed.tech/tags/ui.md>), [ui-components](<https://devfeed.tech/tags/ui-components.md>)

## AI overview

The article proposes adding object-oriented functionality directly to CSS to address the debate around Object Oriented CSS (OOCSS). It explains how reusable classes support complex UI components and discusses why Sass preprocessors do not fully solve the problem.

## Source excerpt

In CSS we often code the same visual components over and over again -- even within the same project. It's embarrassing how many separate times in my career I've coded a two-column layout, or tabbed navigation, or a dropdown menu, or a popup (and the list goes on).