From 3ba66f120bae9194fddf393e84a16eb66a3bd652 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Tue, 21 Mar 2023 21:01:00 +0000 Subject: [PATCH] daily-email: add 2023-03-21 --- src/daily-emails/2023-03-21.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 src/daily-emails/2023-03-21.md diff --git a/src/daily-emails/2023-03-21.md b/src/daily-emails/2023-03-21.md new file mode 100644 index 00000000..9567c250 --- /dev/null +++ b/src/daily-emails/2023-03-21.md @@ -0,0 +1,19 @@ +--- +title: > + There isn't a standard "Tailwind-looking" site +pubDate: 2023-03-21 +permalink: > + archive/2023/03/21/there-isnt-a-tailwind-looking-site +tags: + - tailwind-css +--- + +When looking at some websites, you can tell that it was built using a certain CSS framework. + +Whether it's using a standard component like a navbar or card, or it's using the default colour palette, you can confidently know that website uses ___. + +As Tailwind includes no components (other than the `container`) and only has low-level utility classes for things like spacing and colours (amongst many other things), you can build radically different-looking websites with the same classes. + +There are some [examples of UIs that I've rebuilt](https://www.oliverdavies.uk/blog/uis-ive-rebuilt-tailwind-css) and some websites that I show in my [Taking Flight with Tailwind CSS talk](https://www.oliverdavies.uk/talks/taking-flight-with-tailwind-css). + +If you take a look, you'll see what I mean.