Complex theming

[PVince81]

Requirements

• Exchange assets (icons, buttons, ...)
• Size of HTML elements (logo,
• Margins, paddings, sizes (e.g., height of top bar)
• Consent on login => needs separate extension, not theming
• Ability to change arbitrary strings and translations (ex: User types in sharing (e.g. "Guest" => "EXTERNAL"; GC))

[PVince81]

• have a look at existing Phoenix internal theme to find out which bits we needed to adjust (texts, etc) and define extension points to allow such extensions

[PVince81]

4d for the diff

[PVince81]

we should work on the diff first in case we find more items to discuss for complex theming

[PVince81]

Possible extension of requirements:

• ability for example to decide whether to always hide or not the file actions
• customize / replace share indicators: Extension point sharing indicators for complex theming #2895

Idea: split this ticket further into:

• complex theming that is about replacing stuff visually (string, margin, icons)
• customizing which is about writing extensions and modifying visual behavior ?

[PVince81]

• important to discuss: with complex theming, how to provide alignment on mobile and desktop clients, considering the broad scope of customizations ?

[pascalwengerter]

I guess this can been closed/has been addressed via #9698? I'd prefer smaller and more actionable tickets going forward