I think I might be able to pull of retrocompatibility in the end.
I do not guarenty it but it looks like it might be acheivable to still generate themes that works across all versions of Keycloak.

The new multi valued attribute requires some work to get validated in realtime on the frontend side:

I'm on it

Thanks to https://github.com/jcputney/keycloak-theme-additional-info-extension we will finaly have proper clientside password validation let's go!

For reference: https://keycloak.discourse.group/t/make-password-policies-available-to-freemarker/11632

I made good progress this week end but it will be at least another week befor this get merged

It's taking some time because I need to implement the logic for real-time client-side validation of user profile attributes. The default Keycloak theme lacks any form of client-side validation.

Trust me, the wait will be worth it for the enhanced user experience compared to the default Keycloak theme!

There will no longer be two different pages for register.ftl and register-user-profile.ftl. Just a single page. And this while remaining backward compatible with Keycloak down to version 11.
This is a big win.
Especially if you don't know precisely on which version of Keycloak your theme will be deployed.
It means that Keycloakify themes will have a whider range of supported Keycloak version that any vanilla theme.

Sorry it's taking longer than expected. I don't want to release an half baked major.

Keeping track of pages that have been added/updated:

• delete-credential.ftl
• login-update-profile.ftl
• login.ftl
• register.ftl
• select-authenticator.ftl
• templat.ftl
• update-email.ftl
• user-profile-commons.ftl
• webauthn-autenticate.ftl
• webauthn-register.ftl
• code.ftl
• delete-account-confirm.ftl
• error.ftl
• frontchannel-logout.ftl
• idp-review-user-profile.ftl
• info.ftl
• login-config-totp.ftl
• login-idp-link-confirm.ftl
• login-idp-link-email.ftl
• login-oauth-grant.ftl
• login-oauth2-device-verify-user-code.ftl
• login-otp.ftl
• login-page-expired.ftl
• login-password.ftl
• login-recovery-authn-code-config.ftl
• login-recovery-authn-code-input.ftl
• login-reset-otp.ftl
• login-reset-password.ftl
• login-update-password.ftl
• login-username.ftl
• login-verify-email.ftl
• login-x509-info.ftl
• logout-confirm.ftl
• saml-post-form.ftl
• webauthn-error.ftl
• tems.ftl

every lpages of the login theme are now implemented by Keycloakify and up to date with Keycloak v24 🎊

We're getting there for real.

Still some bugs to fix and testing to do but the codebase is there.

Apologies for the delay, everyone. I'm working hard to get this shipped as soon as possible. There are still some crucial performance optimizations that need to be addressed. Currently, the generated JAR file is too large, and the build time is too long.

Despite these issues, this release is very solid, and I believe the time saved by the various improvements will make up for the delay. Thank you for your patience and understanding.

This should be my final update before the release, if all goes as planned. Given that this major update unavoidably includes some breaking changes, I've decided to implement all the significant modifications we've been considering for a while now. This has resulted in a bit of feature creep but we're getting there.

The new starter: https://github.com/keycloakify/keycloakify-starter/tree/keycloakify_10

Full update of the documentation website and migrating guide coming up very soon.

I’ve finally completed the CSS level customization documentation:
https://docs.keycloakify.dev/customization-strategies/css-level-customization

In particular, some of you might want to check out the documentation specific to Tailwind: https://docs.keycloakify.dev/customization-strategies/css-level-customization/using-tailwind

Account theme v3 available soon!

There is the starter using Account V3 but the API will probably change and I nee to implement some CLI tooling to make the setup and ejection easyer.

https://github.com/keycloakify/keycloakify-starter/tree/account-spa

Well I'm going to merge this branch even if I'm still not fully ready to release v10.
It's kind of missleading v9 still being the main branch.

For pepole waiting for the dust to have settled for upgrading you can track the official v10 release.

Hello!

Keycloakify v10 has been released.

Here are the migration guides: https://docs.keycloakify.dev/faq-and-help/migration-guides/v9-greater-than-v10

I've done my best, but I'm aware that this is not a smooth upgrade process. I figured that it was best to make all the breaking changes at once, hopefully avoiding the need for more in the future.