uuid:
  - value: fa7c7cc8-f504-4aa7-a068-97c57ff1e1ff
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:18+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: 'Everything is a trade-off'
created:
  - value: '2024-03-15T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:18+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2024/03/15/everything-is-a-trade-off
    langcode: en
body:
  - value: |
      <p>I recently added a custom <code>wrapper</code> class within a Tailwind CSS project.</p>

      <p>It combined the <code>max-w-6xl</code>, <code>mx-auto</code> and <code>px-4</code> classes using <code>@apply</code>, which I rarely use.</p>

      <p>I added it so we didn't have to add the same classes multiple times.</p>

      <p>The advantage was it removed some duplication, but people needed to switch from the Twig template to the CSS file to remember what the <code>wrapper</code> class did.</p>

      <p>This undoes some of the advantages of Tailwind CSS and utility classes - the ability to stay in one file without needing to context switching, and easily reading what classes are on an element and immediately knowing what styles are applied to it.</p>

      <p>Everything is a trade-off.</p>

      <p>You need to decide which option feels right for you.</p>

              
    format: full_html
    processed: |
      <p>I recently added a custom <code>wrapper</code> class within a Tailwind CSS project.</p>

      <p>It combined the <code>max-w-6xl</code>, <code>mx-auto</code> and <code>px-4</code> classes using <code>@apply</code>, which I rarely use.</p>

      <p>I added it so we didn't have to add the same classes multiple times.</p>

      <p>The advantage was it removed some duplication, but people needed to switch from the Twig template to the CSS file to remember what the <code>wrapper</code> class did.</p>

      <p>This undoes some of the advantages of Tailwind CSS and utility classes - the ability to stay in one file without needing to context switching, and easily reading what classes are on an element and immediately knowing what styles are applied to it.</p>

      <p>Everything is a trade-off.</p>

      <p>You need to decide which option feels right for you.</p>

              
    summary: null
field_daily_email_cta: {  }