"theme-component" should be a subcategory instead of a tag

[JammyDodger]

@Decorbuz

In my opinion, I think that the Customization > Theme component tag would serve its purpose better as a subcategory.

I’m definitely up for giving the categories and tags a health-check. There have been a couple of good suggestions about giving the structure a bit of a tweak recently, so I’ll collate all of this together and see where we land. I think anything that makes Meta more intuitive for new people/occasional users can only be a good thing.

@Moin

Just a note about tagging: It seems easier to forget to tag a topic than to forget to choose the category. There are already some untagged themes.

This should be less of an issue now there’s a dedicated Community Moderator. () I think having me sort and organise as I go should cover a lot of that. And we have a decent number of TL3s and TL4s, so hopefully reinforcing a consistent pattern will make it easier for other people to join in too.

@maiki

The difference between a theme component and plugin is already blurry in my head.

I still think of it as Frontend versus Backend changes, but the upgrade to ember has blurred what that means to me now too. It seems like it’s made so many more things possible in a theme/theme component than before (which is great if you’re hosted and don’t have easy access to add a plugin ).

@maiki

If someone asked me what the difference between “plugins” and “theme components” is, my first thought would be: one takes a URL field to install, and the other requires a site rebuild.

I think that’s quite a useful distinction for non-developers. Red = /admin/customize, Yellow = app.yml. I think that’s probably all you really need to know if you’re an admin installing an existing customisation, rather than a developer wanting to make a new one.

Thanks for the suggestion @Decorbuz I’ll put some ideas together, and see what we can do.