# Why you should buy your staff a copy of Every Layout

DevFeed: [Why you should buy your staff a copy of Every Layout](<https://devfeed.tech/articles/why-you-should-buy-your-staff-a-copy-of-every-layout-31229.md>)

Original publisher: [Read original article](<https://every-layout.dev/blog/your-boss-pays/>)

Author: Andy

Published: 2019-07-30T00:00:00Z

Content type: opinion

Language: en

Sources: [The Every Layout Blog](<https://devfeed.tech/sources/the-every-layout-blog.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Design system](<https://devfeed.tech/topics/design-system.md>), [Framework](<https://devfeed.tech/topics/framework.md>)

Tags: [css](<https://devfeed.tech/tags/css.md>), [design-system](<https://devfeed.tech/tags/design-system.md>), [framework](<https://devfeed.tech/tags/framework.md>), [front-end](<https://devfeed.tech/tags/front-end.md>)

## AI overview

This opinion article argues that employers should purchase Every Layout for staff training. It presents CSS knowledge and simpler, browser-oriented layouts as ways to reduce mistakes and technical debt, while describing the layouts as portable and interoperable across projects.

## Source excerpt

Dear bosses, You have probably been sent this link by a staff member who would like you to buy them a copy of Every Layout. In this post, I'll outline some benefits that you, the boss, can enjoy if you invest in your staff's learning and training by purchasing a copy of Every Layout. When you understand CSS, you generally make fewer mistakes So many mistakes--especially with CSS--can be directly attributed to a lack of knowledge, but you only get that knowledge from learning and experience. We share our vast, combined experience in Every Layout to give people a head-start. CSS is hard, but what we do with Every Layout is demonstrate how keeping things as simple as possible can give your CSS the most power. We leverage the power of the browser and guide it, rather than micro-manage it, for a much more resilient front-end. This approach is completely valid for building a tiny blog, all the way up to a huge design system. We leverage the power of the browser and guide it, rather than micro-manage it We're convinced that our approach in Every Layout will reduce mistakes. In fact, we know it will, because that approach has served us both very well in our combined experience of over 20 years, working on huge projects and tiny projects alike. Good CSS knowledge will help to reduce technical debt CSS is great, but when you over-engineer and over-complicate it, it can get pretty hairy, pretty quickly. A common, knee-jerk response to this conundrum is to employ the use of a CSS-in-JS library or heavy-duty framework, but that is like taking out a Wonga loan to pay off your house. Technical debt is incredibly expensive, and with modern, all-encompassing web-tooling, the interest rates can be extortionate. In contrast to this, the content we created for Every Layout encourages you to write very powerful layouts, with a tiny, native footprint. These layouts are also portable and interoperable, which means that you can very likely use them across most of your team's projects. Using