64 lines
2.8 KiB
YAML
64 lines
2.8 KiB
YAML
uuid:
|
|
- value: a2dfa0ba-1a95-4b4c-9471-7f0274ae69bf
|
|
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:10+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 CSS v4, with even more CSS'
|
|
created:
|
|
- value: '2024-07-16T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:10+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/07/16/tailwind-css-v4--with-even-more-css
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>As someone <a href="/blog/uis-ive-rebuilt-tailwind-css">who has been using Tailwind CSS</a> since before 1.0, I'm looking forward to the next major version - Tailwind CSS v4.</p>
|
|
|
|
<p>A main difference compared to previous versions is that it will be configured in CSS using CSS variables (aka custom properties).</p>
|
|
|
|
<p>No more <code>tailwind.config.js</code> configuration files, just variables like <code>--color-blue-100</code>.</p>
|
|
|
|
<p>As I <a href="/daily/2024/07/15/the-power-of-arbitrary-classes">already use CSS variables in some situations</a>, I like that it will make it easier to re-use them within Tailwind and give a more consistent experience.</p>
|
|
|
|
<p>As well as simple variables, such as colours and spacing, I'm interested to see how everything else will translate to the new configuration approach in Tailwind v4, as well as anything else new that will be included.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>As someone <a href="/blog/uis-ive-rebuilt-tailwind-css">who has been using Tailwind CSS</a> since before 1.0, I'm looking forward to the next major version - Tailwind CSS v4.</p>
|
|
|
|
<p>A main difference compared to previous versions is that it will be configured in CSS using CSS variables (aka custom properties).</p>
|
|
|
|
<p>No more <code>tailwind.config.js</code> configuration files, just variables like <code>--color-blue-100</code>.</p>
|
|
|
|
<p>As I <a href="/daily/2024/07/15/the-power-of-arbitrary-classes">already use CSS variables in some situations</a>, I like that it will make it easier to re-use them within Tailwind and give a more consistent experience.</p>
|
|
|
|
<p>As well as simple variables, such as colours and spacing, I'm interested to see how everything else will translate to the new configuration approach in Tailwind v4, as well as anything else new that will be included.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|