Should we improve the default UI/UX for generated applications in Grails 8

[jamesfredley]

Currently generated applications plus core plugins including fields and scaffolding generate a fairly stock Bootstrap 5 based design.

There are a number of open source themes which could be incorporated in generated applications to provide an improved UI/UX for generated applications.

Examples (all MIT licensed, some have pro/paid version, but would be unnecessary for a simple generated Grails app):
https://github.com/ColorlibHQ/AdminLTE
https://github.com/coreui/coreui-free-bootstrap-admin-template
https://github.com/tabler/tabler
https://github.com/adminkit/adminkit
https://github.com/ColorlibHQ/gentelella

Or we could go further moving from Bootstrap to Tailwind (all MIT licensed, some have pro/paid version, but would be unnecessary for a simple generated Grails app):
https://github.com/themesberg/flowbite-admin-dashboard
https://github.com/themesberg/tailwind-dashboard-windster
https://github.com/htmlstreamofficial/preline
https://github.com/TailAdmin/tailadmin-free-tailwind-dashboard-template
https://github.com/ColorlibHQ/gentelella
https://github.com/estevanmaito/windmill-dashboard?tab=readme-ov-file

[matrei]

Yes, this should definitely be on the roadmap for 8 🚀

[sbglasius]

It would be cool, if start.grails.org would let you choose what theme your default project would create. That would be a new touch.

[richardvil]

I believe this is a valuable opportunity to modernize the developer experience without sacrificing grails core principles. Freshly generated application includes bootstrap with minimal styling, you can apply fields plugin and the scaffolding system, but I think they lack the flexibility needed to seamlessly apply third-party libraries or deeper customization (must say that I haven't worked with fields or scaffolding for a long time). This approach works, but it remains limited, and it creates a noticeable gap when compared to the first-run experience offered by other frameworks.

From my perspective, grails should css-framework-agnostic. Forcing a specific styling stack can introduce unnecessary dependencies, complicate the integration of external libraries and discourage teams that prefer alternative tools. That said, I also believe many developers would benefit from having an optional, opinionated default UI layer that accelerates initial development, provides a clear structure for layouts and forms, and establishes a baseline of UX consistency.

Additionally, I would strongly consider integrating Spring Security UI, the functionality it provides is essential for rapid application development.

[jamesfredley]

Grails provides a default, which I believe is a good idea, especially for new users and then allows you define anything you want, which replaces the default.

Right now I don't use any part of the default html, css or js, in any of my applications, but when I generate a sample application or demonstrate Grails, I wish it looked more like one of those themes by default.

[richardvil]

Exactly, that's point of a "ui starter pack" but if you attach it to a particular template or theme you're forced to maintain it with all his dependencies. A more efficient approach would be support "most popular" css frameworks and use his own css classes but providing a minimal structure needed by any kind of application: dashboard, form, tables, etc. Spring security UI would be a must in order to create a ready-to-go experience. Currently I'm working with alpinejs creating taglib components and I've to said that is a great tool to combine with gsp.