92 lines
6.6 KiB
YAML
92 lines
6.6 KiB
YAML
uuid:
|
|
- value: 7fce2f3b-7564-40a0-8dfc-741c66a3b993
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T09:00:55+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: 'My Tailwind CSS origin story'
|
|
created:
|
|
- value: '2022-09-07T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:55+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2022/09/07/my-tailwind-css-origin-story
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>Tomorrow night, I'm attending one of Simon Vrachliotis (simonswiss)'s Pro Tailwind workshops, so I thought that it would be a good time, as Simon has done himself recently on the Navbar podcast, to describe how I started using Tailwind CSS.</p>
|
|
|
|
<p>I remember watching a lot of Adam Wathan's live streams on YouTube before Tailwind CSS, and I remember when he started a new project - a SaaS product called KiteTail.</p>
|
|
|
|
<p>It was a Laravel and Vue.js project, and although I'm not a Laravel Developer primarily, I got a lot of other information from Adam's streams about automated testing, test-driven development, and Vue.js as I was learning Vue at the time.</p>
|
|
|
|
<p>One of the episodes was about styling a card component using some styles that Adam was copying between projects - which would eventually be the starting point for Tailwind CSS.</p>
|
|
|
|
<p>In fact, I think I watched some of the episode and stopped as I was happy with the Sass and BEM or SMACSS approach that I was using at the time, and didn't initially see the value of the utility CSS approach that I was seeing for the first time (everyone has a similar reaction initially).</p>
|
|
|
|
<p>After a while, I did re-visit it but because Tailwind CSS wasn't released as it's own project yet, I (like Simon) started to experiment with Tachyons - another utility CSS library.</p>
|
|
|
|
<p>I rebuilt a particularly tricky component that I'd just finished working on and had caused me some issues, and managed to re-do it in only a few minutes.</p>
|
|
|
|
<p>I started to use Tachyons on some personal and client projects as a layer on other frameworks like Bootstrap and Bulma, and later moved on to Tailwind CSS once it has been released.</p>
|
|
|
|
<p>I was working in this way on a project when I released that I could use Tailwind for all of the styling instead of just adding small sprinklings of utilities here and there. I refactored everything and removed the other framework that I'd been using - leaving just Tailwind CSS.</p>
|
|
|
|
<p>With the exception of some legacy projects, now I use Tailwind CSS exclusively and have used it for a number of projects. I've given lunch and learn sessions to teams that I've worked on, <a href="/presentations/taking-flight-tailwind-css">presented a Tailwind CSS talk</a> at a number of PHP, Drupal, WordPress, and JavaScript events, and maintain <a href="https://www.drupal.org/project/tailwindcss">a starter-kit theme</a> for using Tailwind in custom Drupal themes.</p>
|
|
|
|
<p>I've also rebuilt a <a href="/blog/uis-ive-rebuilt-tailwind-css">number of existing sites</a> as examples and written some <a href="/blog/tags/tailwind-css">Tailwind CSS related blog posts</a>.</p>
|
|
|
|
<p>I'm looking forward to attending Simon's workshop tomorrow and quickly putting that knowledge to use in the next phase of a project that I'm currently working on.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>Tomorrow night, I'm attending one of Simon Vrachliotis (simonswiss)'s Pro Tailwind workshops, so I thought that it would be a good time, as Simon has done himself recently on the Navbar podcast, to describe how I started using Tailwind CSS.</p>
|
|
|
|
<p>I remember watching a lot of Adam Wathan's live streams on YouTube before Tailwind CSS, and I remember when he started a new project - a SaaS product called KiteTail.</p>
|
|
|
|
<p>It was a Laravel and Vue.js project, and although I'm not a Laravel Developer primarily, I got a lot of other information from Adam's streams about automated testing, test-driven development, and Vue.js as I was learning Vue at the time.</p>
|
|
|
|
<p>One of the episodes was about styling a card component using some styles that Adam was copying between projects - which would eventually be the starting point for Tailwind CSS.</p>
|
|
|
|
<p>In fact, I think I watched some of the episode and stopped as I was happy with the Sass and BEM or SMACSS approach that I was using at the time, and didn't initially see the value of the utility CSS approach that I was seeing for the first time (everyone has a similar reaction initially).</p>
|
|
|
|
<p>After a while, I did re-visit it but because Tailwind CSS wasn't released as it's own project yet, I (like Simon) started to experiment with Tachyons - another utility CSS library.</p>
|
|
|
|
<p>I rebuilt a particularly tricky component that I'd just finished working on and had caused me some issues, and managed to re-do it in only a few minutes.</p>
|
|
|
|
<p>I started to use Tachyons on some personal and client projects as a layer on other frameworks like Bootstrap and Bulma, and later moved on to Tailwind CSS once it has been released.</p>
|
|
|
|
<p>I was working in this way on a project when I released that I could use Tailwind for all of the styling instead of just adding small sprinklings of utilities here and there. I refactored everything and removed the other framework that I'd been using - leaving just Tailwind CSS.</p>
|
|
|
|
<p>With the exception of some legacy projects, now I use Tailwind CSS exclusively and have used it for a number of projects. I've given lunch and learn sessions to teams that I've worked on, <a href="/presentations/taking-flight-tailwind-css">presented a Tailwind CSS talk</a> at a number of PHP, Drupal, WordPress, and JavaScript events, and maintain <a href="https://www.drupal.org/project/tailwindcss">a starter-kit theme</a> for using Tailwind in custom Drupal themes.</p>
|
|
|
|
<p>I've also rebuilt a <a href="/blog/uis-ive-rebuilt-tailwind-css">number of existing sites</a> as examples and written some <a href="/blog/tags/tailwind-css">Tailwind CSS related blog posts</a>.</p>
|
|
|
|
<p>I'm looking forward to attending Simon's workshop tomorrow and quickly putting that knowledge to use in the next phase of a project that I'm currently working on.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|