Customizing handlebars templates

[sarahann (Sarah)]

Thanks for the super quick reply!! This has been super helpful!

But I have a few more questions now.

@david

Overriding a template will “replace” it. Plugin outlets are simply points in the page that you can “insert” content into. If you want to add content, a plugin outlet might be enough. Overriding templates should always be a last resort.

I was wondering more if the plugin outlet (Developing Discourse Plugins - Part 1 - Create a basic plugin) and the pluginAPI (A versioned API for client side plugins) do the same thing? Their implementation is different, as one is a plugin added to discourse and the other is part of the HTML/JS. Is one of these methods preferred? Cause you also mentioned that:

@david

Plugin outlets are a far better way to extend things, they shouldn’t be broken by changes made to Discourse.

So does that mean that the pluginAPI isn’t as resilient to changes as the plugin outlets?

@david

The easiest way is through CSS changes in a theme as you mentioned. You could have a look at this theme, which @joebuhlig uses to hide a number of discourse features:

I was hoping not to use ‘display: none’. I was snooping through some sites that have customized Discourse and came across this one. Overwatch Forums
It looks really clean, but lots of the out-of-the-box functionality is removed from the UI. I don’t see any ‘display: none’ to remove the functionality. Could it be that Blizzard used the pluginAPI or plugin outlet to replace some of the handlebars files, and omitted some of the code?