I would like to share some ideas where we can go to make this starterkit interesting in 2026, relevant with what actually happens in Drupal and promoting its transition. We are currently in version 5 and there are two major topics. The order is not random:

  1. Upgrading Tailwind to version 4.
  2. Make this starterkit encouraging to use Canvas module - adding some very basic Single Directory Components and changing bit a philosophy in template files

Both may sound like a change breaking enough to release a new major version. The question is, how are we gonna approach it in terms of versioning?

  • Do we leave the version 5.x as it is and we put all changes from now to version 6.x? - we clearly indicate a milestone that development has been renewed and cutting ourselves from the past
  • Do we migrate to Tailwind 4 on version 5.x and then keep the Canvas stuff for version 6.x? - we let people choose whether they want to use the latest Drupal canvas features, or they prefer to go classic templating (but still, with the latest Tailwind CSS features)

What do you think is better? Looking to hear your words as a maintainers.

Comments

firflant created an issue.

ravi kant’s picture

ravi kant commented

Thanks @firflant for raising this topic.

Both points make a lot of sense regarding the upcoming upgrades. I would suggest introducing the Canvas compatibility changes in the 5.x branch first. After that, we can plan the Tailwind upgrade as part of the 6.x release.

This approach would allow us to improve Canvas support without introducing too many breaking changes at once, while reserving the Tailwind upgrade for the next major version.

firflant’s picture

firflant
Location Poland
commented

Thank you @ravi-kant. It implicates, that the canvas-prepared version should be also suited properly for the classic blocks approach (including fixing all the current issues) - let's agree on that.