Re: [keycloak-dev] initial theme feedback

There is reasoning behind not having the default themes exploded in standalone/configuration/themes: * Default themes should not be modified or deleted * You don't need those files unless you're overriding templates. That's an "advanced feature", so I believe users that wants to do that can extract them from source files or jar without difficulty * If you're just styling the current templates, you do not need to refer to the files from the default themes * I didn't want to always require a theme folder * On LiveOak I want the default themes loaded by class-path, and we'll probably let users upload custom themes to mongo-fs rather than the file-system That being said, if you really, really want to have these themes in the standalone/configuration/themes that's should be possible by copying them in there from the jar when building the dist. The "folder provider" now has a higher priority than the "classpath provider", so if a theme with the same name exists both places it will be loaded from the "folder provider". ----- Original Message -----