@boris Are we able to have a header like the Docker Forum?
It’s in the HEADER tag and and scrolls up until only the menu is left.
Anything is possible. There is a thread in #team where I documented different header link components I experimented with.
I think a custom theme would be a good thing. Someone will need to take responsibility for that, and either raise funds or spend time learning the theming system or both.
Some info here that might be helpful but not sure how current this is:
There is a request to import “Sams minimal theme” Sam's personal "minimal" topic list design - theme - Discourse Meta … I could find it in the “import list” but I didn’t know it it still works.
Should I import it, or can it break something?
Themes are pretty benign (no backend code) — so go for it!
You can make a backup first in admin settings.
I’d be a tiny bit worried about supporting additional themes. The potential problem being that if in the future we want to make custom tweaks to the UI HTML by directly modifying the templates, we’d have to make them in all the themes we’ve installed.
The alternative is to point people at Greasemonkey etc for customisation, which obviously would be unaffected by support concerns.
Discourse themes are similar to TW themes. Eg: The Simple Theme only changes some elements from the overview list. The difference to TW is, that they use handlebars as a templating language.
Hi @pmario I understand, but my concern is that we should try to keep this installation streamlined and as simple as we can in order to reduce the administrative overhead over time. For example, supporting multiple themes means that we’ll have to test all of them before we make visual changes to the system. Or when somebody asks how to do something, they won’t necessarily recognise the screenshot if they happen to be using a different theme. We should keep the system simple, and shift the burden for arcane use cases onto our users.