Is there a naming convention for theme component projects, so that they’re easily recognizable as such? When seeing the folder on disk, or the repo on GitHub or the project on GitLab or another code forge, it’d be useful to be able to see at one glance that this is to be used with Discourse it’s …

We don’t enforce any naming conventions… the Discourse team will often prefix themes and components with discourse- but it’s not universal. Beyond the directory name, hopefully the readme will include a little context that it’s for Discourse… otherwise themes and theme-components always have an abo…

I use discourse-tc- to signify a theme component because it’s good practice and handy to distinguish those from themes and plugins.

[Bild] merefield: because it’s good practice and handy to distinguish those from themes and plugins. I like that, because it’s short-ish, yet informative. What naming convention (if any) do you use for themes and plugins?

Same here discourse-foo for plugins discourse-theme-foo for full themes discourse-tc-foo for theme components

Gibt es eine Namenskonvention für Theme Component Projekte?

Entwickler

RGJ (Richard - Communiteq) 16. März 2026 um 22:40 5

Dasselbe hier

discourse-foo für Plugins
discourse-theme-foo für vollständige Themes
discourse-tc-foo für Theme-Komponenten

Thema		Antworten	Aufrufe
"theme-component" should be a subcategory instead of a tag Site feedback	15	1666	18. Juli 2022
Developing Discourse Themes & Theme Components Developer Guides reference , tutorial , theme-guides	14	107677	18. März 2025
When to use a plugin vs theme component? Development css	12	760	1. März 2024
Beginner's guide to using Discourse Themes Site Management reference , customization	10	84414	22. Juni 2026
Why isn't the checklist plugin a Theme Component? Development checklist	4	128	4. September 2025

Gibt es eine Namenskonvention für Theme Component Projekte?

Verwandte Themen