docs: start construction of graveyard

docs/src/contents/04.progress/03.ArchitecturalGraveyard.mdx

@@ -8,4 +8,12 @@ Senior engineers build things because they should.
 
 This graveyard documents the journey between those two mindsets.
 
----
+---
+
+## TailwindCSS (Nov 2023 - May 2026)
+
+When you prompt an AI agent, regardless of the model you're using, to vibe-code a frontend application, 101% of the time, the CSS framework in the generated code will default to TailwindCSS. I'm not exaggerating at all. It's not hard to infer the reason behind this. Tailwind has been sitting on the throne of the United Kingdom of CSS Frameworks and Libraries for years, and, needless to say, most of the codebase in the models' training dataset is written in Tailwind.
+
+Tailwind might not be the first UI framework to have introduced a utility-based styling approach, but to be quite honest, it is definitely the framework that excels in it. I mean, styling a component without having to spend your brain cells thinking about what class name to assign to the element and what CSS selector that corresponds to it, subsequently stripping away a huge chunk of mental load during development. This mental energy that has been freed up can thus be used in something more productive and creative, to concentrate on what you want your product to actually look like. Even for myself, when I was working on other projects outside LifeForge, Tailwind is still my top preference when it comes to styling.
+
+![Vanilla CSS vs Tailwind](https://raw.githubusercontent.com/LifeForge-app/lifeforge-docs-media/main/assets/graveyard/vanilla-vs-tailwind.webp)

docs/src/index.css

@@ -6,7 +6,7 @@
 @import 'react-medium-image-zoom/dist/styles.css';
 
 :root {
-  --custom-font-scale: 1.1 !important;
+  --custom-font-scale: 1.2 !important;
 }
 
 *:not(code *) {