<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Give 'n' Go</title><link>https://give-n-go.co/tags/architecture/</link><description>Recent content in Architecture on Give 'n' Go</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 10 Jun 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://give-n-go.co/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>CSS Architecture for Small Visual Projects</title><link>https://give-n-go.co/guides/css-architecture-for-small-visual-projects/</link><pubDate>Mon, 10 Jun 2024 00:00:00 +0000</pubDate><guid>https://give-n-go.co/guides/css-architecture-for-small-visual-projects/</guid><description>&lt;p>CSS architecture for large applications gets plenty of attention. Design systems, utility-first frameworks, CSS-in-JS, and scoped styles all address the problem of scaling CSS across large teams and complex component trees. But small visual projects, the kind that make up most front-end gallery work, component experiments, and personal sites, have different constraints and deserve their own architectural approach. This guide covers how to structure CSS for projects with 10 to 50 components, one to three contributors, and a focus on visual quality rather than organizational scale. We address file structure, naming discipline, custom property strategy, specificity management, and the pragmatic compromises that keep small projects maintainable without drowning in process overhead.&lt;/p></description></item></channel></rss>