{
    "uuid": [
        {
            "value": "805363c0-2306-47f5-b9ba-57995ebe12b3"
        }
    ],
    "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:04+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 is so easy to set up"
        }
    ],
    "created": [
        {
            "value": "2024-11-19T00:00:00+00:00"
        }
    ],
    "changed": [
        {
            "value": "2025-05-11T09:00:04+00:00"
        }
    ],
    "promote": [
        {
            "value": false
        }
    ],
    "sticky": [
        {
            "value": false
        }
    ],
    "default_langcode": [
        {
            "value": true
        }
    ],
    "revision_translation_affected": [
        {
            "value": true
        }
    ],
    "path": [
        {
            "alias": "\/daily\/2024\/11\/19\/tailwind-css-v4-is-so-easy-to-set-up",
            "langcode": "en"
        }
    ],
    "body": [
        {
            "value": "\n          <p>I've recently been working with a client to kickstart the front-end development on their Drupal upgrade project from Drupal 7 to 10.<\/p>\n\n<p>They've been working hard on the back-end code and migrations, but hadn't done anything on the front-end yet.<\/p>\n\n<p>I was asked to come in and set up a new theme for them and provide some training to get them going.<\/p>\n\n<p>A requirement they mentioned was to make it themable, so they could later change colours of buttons and other elements based on the page type being viewed or if they added sub-sites in the future.<\/p>\n\n<p>This is something I've done a lot with Tailwind CSS and, as it's <a href=\"\/blog\/uis-ive-rebuilt-tailwind-css\">the CSS framework I'm most familiar with<\/a>, we decided to go with Tailwind CSS - and specifically the alpha version of Tailwind CSS v4.<\/p>\n\n<p>Although it's still in an alpha phase, I've been experimenting with Tailwind v4 in personal projects and on some live streams and it seemed stable enough to use in production.<\/p>\n\n<p>It also makes theming a lot easier as it uses CSS variables everywhere, which made it a no-brainer for this project.<\/p>\n\n<p>Aside from the new features, the setup for Tailwind CSS is so easy and straight forward.<\/p>\n\n<p>There's no JavaScript configuration file and everything is done in a CSS file, making it simpler to set up and more consistent if you need to write CSS anyway to add custom fonts or work with CSS variables - these are no longer in separate places and are now combined in one stylesheet.<\/p>\n\n<p>All the colour configuration and adding plugins is done in the CSS file and Tailwind will find the content files to scan automatically so you no longer need to declare where your template files are - it just knows.<\/p>\n\n<p>It's worked well for this project, and I'll look forward to using Tailwind v4 more on YouTube and for personal and client projects.<\/p>\n\n        ",
            "format": "full_html",
            "processed": "\n          <p>I've recently been working with a client to kickstart the front-end development on their Drupal upgrade project from Drupal 7 to 10.<\/p>\n\n<p>They've been working hard on the back-end code and migrations, but hadn't done anything on the front-end yet.<\/p>\n\n<p>I was asked to come in and set up a new theme for them and provide some training to get them going.<\/p>\n\n<p>A requirement they mentioned was to make it themable, so they could later change colours of buttons and other elements based on the page type being viewed or if they added sub-sites in the future.<\/p>\n\n<p>This is something I've done a lot with Tailwind CSS and, as it's <a href=\"http:\/\/default\/blog\/uis-ive-rebuilt-tailwind-css\">the CSS framework I'm most familiar with<\/a>, we decided to go with Tailwind CSS - and specifically the alpha version of Tailwind CSS v4.<\/p>\n\n<p>Although it's still in an alpha phase, I've been experimenting with Tailwind v4 in personal projects and on some live streams and it seemed stable enough to use in production.<\/p>\n\n<p>It also makes theming a lot easier as it uses CSS variables everywhere, which made it a no-brainer for this project.<\/p>\n\n<p>Aside from the new features, the setup for Tailwind CSS is so easy and straight forward.<\/p>\n\n<p>There's no JavaScript configuration file and everything is done in a CSS file, making it simpler to set up and more consistent if you need to write CSS anyway to add custom fonts or work with CSS variables - these are no longer in separate places and are now combined in one stylesheet.<\/p>\n\n<p>All the colour configuration and adding plugins is done in the CSS file and Tailwind will find the content files to scan automatically so you no longer need to declare where your template files are - it just knows.<\/p>\n\n<p>It's worked well for this project, and I'll look forward to using Tailwind v4 more on YouTube and for personal and client projects.<\/p>\n\n        ",
            "summary": null
        }
    ]
}