{ "uuid": [ { "value": "b1a76740-f08d-4af6-a37a-a1bdf73fef5c" } ], "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:22+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": "Using Tailwind CSS is a great way to learn CSS" } ], "created": [ { "value": "2024-01-09T00:00:00+00:00" } ], "changed": [ { "value": "2025-05-11T09:00:22+00:00" } ], "promote": [ { "value": false } ], "sticky": [ { "value": false } ], "default_langcode": [ { "value": true } ], "revision_translation_affected": [ { "value": true } ], "path": [ { "alias": "\/daily\/2024\/01\/09\/using-tailwind-css-is-a-great-way-to-learn-css", "langcode": "en" } ], "body": [ { "value": "\n

I was in a pair programming session today, working on some Twig components with Tailwind CSS.<\/p>\n\n

We knew what we needed to implement and did so based on an example from a Tailwind component library and some additional styles.<\/p>\n\n

After implementing the feature, we could review the classes we added and review what each did.<\/p>\n\n

We could easily move or remove a class and see what effect it had.<\/p>\n\n

Something nice is that the Tailwind classes usually relate to what CSS they're applying, such as block<\/code> and flex<\/code> for display<\/code> and relative<\/code> and absolute<\/code> for positioning.<\/p>\n\n

This makes Tailwind a great way to learn CSS compared to other frameworks that give you prebuilt HTML and expect you to add a generic class like card<\/code>.<\/p>\n\n

In that case, the knowledge is hidden within a stylesheet the Developer doesn't see, which makes it harder to read and learn from.<\/p>\n\n

Other utility-class frameworks have shorter class names that are less readable.<\/p>\n\n

Tailwind strikes the perfect balance, in my opinion.<\/p>\n\n ", "format": "full_html", "processed": "\n

I was in a pair programming session today, working on some Twig components with Tailwind CSS.<\/p>\n\n

We knew what we needed to implement and did so based on an example from a Tailwind component library and some additional styles.<\/p>\n\n

After implementing the feature, we could review the classes we added and review what each did.<\/p>\n\n

We could easily move or remove a class and see what effect it had.<\/p>\n\n

Something nice is that the Tailwind classes usually relate to what CSS they're applying, such as block<\/code> and flex<\/code> for display<\/code> and relative<\/code> and absolute<\/code> for positioning.<\/p>\n\n

This makes Tailwind a great way to learn CSS compared to other frameworks that give you prebuilt HTML and expect you to add a generic class like card<\/code>.<\/p>\n\n

In that case, the knowledge is hidden within a stylesheet the Developer doesn't see, which makes it harder to read and learn from.<\/p>\n\n

Other utility-class frameworks have shorter class names that are less readable.<\/p>\n\n

Tailwind strikes the perfect balance, in my opinion.<\/p>\n\n ", "summary": null } ], "feeds_item": [ { "imported": "1970-01-01T00:33:45+00:00", "guid": null, "hash": "7b51105f14f48cc301c0e7b3db261bab", "target_type": "feeds_feed", "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76" } ] }