# How to override \`admin.hbs\`

**URL:** <https://meta.discourse.org/t/how-to-override-admin-hbs/98307>\
**Category:** Development\
**Created:** [September 28, 2018, 8:59pm UTC](https://meta.discourse.org/t/how-to-override-admin-hbs/98307 "2018-09-28T20:59:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![gdpelican](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gdpelican/32/81308_2.png) [@gdpelican](https://meta.discourse.org/u/gdpelican)\
**Post date:** [September 28, 2018, 9:25pm UTC](https://meta.discourse.org/t/how-to-override-admin-hbs/98307/2 "2018-09-28T21:25:54Z")

</div>

Overriding templates is a fairly nuclear solution, and some one-off fiddly javascript or css like

```plaintext
// NB I am pseudocode
$('.api-nav-item').attr('disabled', 'true')
.api-nav-item { display: none; }

```

would definitely serve you better here if you can get away with it.

If you need to override a whole template, theme component is the simpler way that I know of, with something like

```plaintext
<script type="text/x-handlebars" data-template-name="admin">
  <div>Hello world!</div>
</script>

```

If your plugin is going to go onto a bunch of instances, or you need to automate the installation more for whatever reason, you can go with my jack-wild solution from [mingle](https://github.com/gdpelican/mingle/blob/master/app/extras/theme_component_seed.rb), which automatically populates a theme component when the plugin is installed (but note that this is well within the realm of mad science 👨‍🔬).

---

_[View the full topic](https://meta.discourse.org/t/how-to-override-admin-hbs/98307)._