uuid:
  - value: 5715449a-bcad-41cd-bdb7-252d43b3ebcf
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:48+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: |
      Tailwind's classes are your classes
created:
  - value: '2023-01-20T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:48+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2023/01/20/tailwinds-classes-are-your-classes
    langcode: en
body:
  - value: |
      <p>In my <a href="/talks/taking-flight-with-tailwind-css">Taking Flight with Tailwind CSS talk</a>, I've described Tailwind as a CSS utility class generator. You write a configuration file that Tailwind reads and generates the appropriate classes.</p>

      <p>Yesterday I mentioned the <a href="https://phpsw.uk">PHP South West user group</a> website. It's a project that <a href="https://twitter.com/opdavies/status/934488762276564993">I worked on in November 2017</a> and uses Tailwind 0.5.</p>

      <p>For me, a big advantage of Tailwind was that once it generates the classes, they are ours. They aren't hidden within the framework or an npm package. We can see them, commit them to version control and keep them for as long as we need.</p>

      <p>Even if the Tailwind CSS framework disappeared tomorrow (I hope it doesn't), I'd be able to continue using the styles that it generated, and my projects would continue to work and look the same.</p>

              
    format: full_html
    processed: |
      <p>In my <a href="/talks/taking-flight-with-tailwind-css">Taking Flight with Tailwind CSS talk</a>, I've described Tailwind as a CSS utility class generator. You write a configuration file that Tailwind reads and generates the appropriate classes.</p>

      <p>Yesterday I mentioned the <a href="https://phpsw.uk">PHP South West user group</a> website. It's a project that <a href="https://twitter.com/opdavies/status/934488762276564993">I worked on in November 2017</a> and uses Tailwind 0.5.</p>

      <p>For me, a big advantage of Tailwind was that once it generates the classes, they are ours. They aren't hidden within the framework or an npm package. We can see them, commit them to version control and keep them for as long as we need.</p>

      <p>Even if the Tailwind CSS framework disappeared tomorrow (I hope it doesn't), I'd be able to continue using the styles that it generated, and my projects would continue to work and look the same.</p>

              
    summary: null
field_daily_email_cta: {  }