Do you have original customisations?

[erlend_sh (Erlend Sogge Heggen)]

@bts

Aside from color scheme and some UI adjustments and simplifications I think the most noticeable thing we did is add a visual header banner for each category. We liked how this looked on some other sites we came across e.g. Flarum and found it nice to have extra visual distinction for categories. This is done with custom HTML in the “after header” section plus some fairly complicated CSS targeting…luckily Discourse has category slugs included in class names!

This looks awesome! Could you share this as a theme (component)?

Structure of themes and theme components

Discourse now supports native themes that can be sourced from a remote git repository, or from a .tar.gz archive. Recently we also added support for branches and private repositories. [56] An example theme is at: https://github.com/SamSaffron/discourse-simple-theme [32] The git repository will be checked for updates (once a day), or by using the Check for Updates button. When changes are detected the Check for Updates button will change to the Update to Latest. [image] To create a theme…

Create and share a font theme component

Discourse supports importing themes containing assets from a remote repository. This allows theme authors to share fonts and images. Create a new git repository with the font mkdir discourse-roboto-theme cd discourse-roboto-theme git init . vim about.json For about.json add a skeleton config file { "name" : "Roboto theme component", "about_url" : "", "license_url": "", "assets": { "roboto": "assets/roboto.woff2" } } Add a LICENSE file, I usually use MIT vim LICENSE …