Comments

opdavies created an issue. See original summary.

opdavies’s picture

opdavies
He/him
Primary language English
Location Wales
commented
Issue summary: View changes
steinmb’s picture

steinmb commented

A little confused here. This one is open, but version 4.0 is still only RC. Are you planning to leapfrog 4.0 or is this plan for the future?

cbrody’s picture

cbrody commented

Hi, just wondering if/when you're planning to update this project to Tailwind v3.x?

opdavies’s picture

opdavies
He/him
Primary language English
Location Wales
commented

I've just opened a new child issue to update to Tailwind 3.x #3257888: Update to Tailwind CSS 3.x.

opdavies’s picture

opdavies
He/him
Primary language English
Location Wales
commented

Are you planning to leapfrog 4.0 or is this plan for the future?

5.x is the current development version where I've been working on breaking changes such as updating Tailwind CSS itself and changing how the CSS is generated - things that I can't do in the 4.x branch.

4.x is still using Tailwind 1.9, and with Tailwind Labs now releasing Tailwind 3, the default version is more out of date that it was before. This might mean that 4.x is a short-lived branch and 5.x becomes the default fairly quickly.

Users of the theme can change whatever they want in their implementations of the theme, of course, as it's supposed to be a starter kit for people's custom themes, but I'm also trying to support the use-case of someone using it for demos or for some other reason and I'm trying to keep the changes backwards-compatible within beta, RC, and stable versions, whilst making any updates to the theme as well as any upstream dependencies - including Tailwind CSS itself.

steinmb’s picture

steinmb commented

@cbrody I think you should open a separate feature request. 3.x contains breaking changes and I think this module have/should —roll a separate main version avoiding breaking existing sites.

https://tailwindcss.com/docs/upgrade-guide

cbrody’s picture

cbrody commented

@steinmb thanks - the project has been updated to Tailwind 3 in version 5 (in alpha). It's currently missing the build tool config provided with previous releases.

matthieuscarset’s picture

matthieuscarset commented

+1 to get this new version moving forward.

Wouldn't it be a good idea to make it D10 compatible?

Also, it would be convenient to make it a starterkit_theme

https://www.drupal.org/docs/core-modules-and-themes/core-themes/starterk...

steinmb’s picture

steinmb commented

@matthieuscarset do you mind creating a feature req. on starter_kit support?

matthieuscarset’s picture

matthieuscarset commented

I don't mind at all but I don't know what the starter_kit support is.

Are you referring to another issue queue?

arefen’s picture

arefen commented

Is this project still alive?

ravi kant’s picture

ravi kant commented

We are happy to announce that we are planning to release a new 6.x version with Tailwind v4 and Canvas compatibility.

ravi kant’s picture

ravi kant commented

Released version 5.0 with bug fixes and canvas compatibility improvements.

duntuk’s picture

duntuk commented

6.x = Tailwind v4

5.x = Tailwind v5

ok... lol

you should make a note to ignore the #13 comment.

ravi kant’s picture

ravi kant commented

Version 5.x uses Tailwind CSS v3, and version 6.x will use Tailwind CSS v4.

valgibson’s picture

valgibson commented

Hi Ravi,

The Drupal Version 6.x (tw 4) is not released yet right? Or is it in the dev-branch? I don't mind if so, because I will use it as a starter kit anyway.
But as far as I could see from the latest comments in git log it is not deployed yet.