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.

[이미지] 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

테마 컴포넌트 프로젝트의 네이밍 컨벤션이 있나요?

개발

RGJ (Richard - Communiteq) 3월 16, 2026, 10:40오후 5

저도 마찬가지입니다

플러그인의 경우 discourse-foo
전체 테마의 경우 discourse-theme-foo
테마 컴포넌트의 경우 discourse-tc-foo

글		댓글	조회수
"theme-component" should be a subcategory instead of a tag Site feedback	15	1866	7월 18, 2022
Developing Discourse Themes & Theme Components Developer Guides reference , tutorial , theme-guides	14	109514	3월 18, 2025
Beginner's guide to using Discourse Themes Site Management reference , customization	12	86118	7월 9, 2026
When to use a plugin vs theme component? Development css	12	957	3월 1, 2024
Why isn't the checklist plugin a Theme Component? Development checklist	4	215	9월 4, 2025

테마 컴포넌트 프로젝트의 네이밍 컨벤션이 있나요?

Related topics