Not sure why a child template is needed, since you only change the main template and just add a custom config file for the child template.

@HLeithner you mean we should modify Cassiopeia directly? What about existent child templates, would they don't break?

Not sure what you mean, if you add options and use the default option the current one it should be the same as the child template since you modified the original template already or do I miss something?

I've installed 6.0.0-alpha2-dev.

Specified the German language file.
de-language won't install. Doesn't matter at the moment.

"NPM Package downloaded: These packages were built on Thu May 29 17:49:52 UTC 2025
These packages were built based on commit f3e6f68 included in pull request 45539"

Does it make sense to install it now? There are open questions above.
(christine2)

Tip to install a language file: got to Extensions: Languages and follow the Details URL link. Copy the downloadurl and use it to fetch the J5 language pack. Use Install Extensions to install it as you would any non-language extension.

Thank you @ceford. Of course I did also before. Will try later again.

Thanks @drmenzelit, comments so far:

1. Colours expose 'primary' colours, is there a default or secondary?
2. Sizes, if we're offering h tag sizes we really need to offer h1 to h6, with weight and line-heights
3. We were unclear on what units we were dealing with, so I think that needs to be clear or selectable

@harald's point seems very pertinent, does anyone else have any input on the difference between a simple config file or providing a full child template.

@ChristineWk thank your for your interest in testing! This is a DRAFT Pr. As you don't have a local development environment, you should wait with tests until the PR is pulished.

@Bodge-IT

1. Bootstrap has primary, secondary, info, alert, etc. colours, if we make all of them changeable, we will end with an endles list of parameters.
2. I don't think it is necessary to offer h4-h6 too. Maybe h4, Bootstrap has also a size for displays > 1200px. Here we will need a description, the size is only for displays > 1200px. Below Bootstrap makes responsive calculations on font size.
3. We / Bootstrap use(s) rem as unit, we can put it on a description.

@Bodge-IT

1. Bootstrap has primary, secondary, info, alert, etc. colours, if we make all of them changeable, we will end with an endless list of parameters.

Could we reduce the amount of visible params by linking conditionals fields to a selector?

Could we reduce the amount of visible params by linking conditionals fields to a selector?
@Bodge-IT
Do you mean something like:
Change Secondary Colours Yes / No - Default No - If Yes display more options?

I don't think, it is a good idea, it would need more logic in the index.php to add / not to add CSS custom properties ...

Normally when you create a child template you have the following folders
css
js
images
scss

This pr only creates the css folder which might confuse some people

@brianteeman that is true .. I will add the folders on my next commit. I'm thinking of a new logo too ...

Closing in favour of #45624