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.

[imagem] 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

Existe uma convenção de nomenclatura para projetos de componentes de tema?

Dev

RGJ (Richard - Communiteq) 16 Março , 2026 22:40 5

O mesmo aqui

discourse-foo para plugins
discourse-theme-foo para temas completos
discourse-tc-foo para componentes de tema

Tópico		Respostas	Vistas
"theme-component" should be a subcategory instead of a tag Site feedback	15	1694	18 Julho , 2022
Developing Discourse Themes & Theme Components Developer Guides reference , tutorial , theme-guides	14	108059	18 Março , 2025
Beginner's guide to using Discourse Themes Site Management reference , customization	12	84937	9 Julho , 2026
When to use a plugin vs theme component? Development css	12	784	1 Março , 2024
Why isn't the checklist plugin a Theme Component? Development checklist	4	141	4 Setembro , 2025

Existe uma convenção de nomenclatura para projetos de componentes de tema?

Related topics