# Getting addons ready to support First-Class Component Templates

**URL:** https://discuss.emberjs.com/t/getting-addons-ready-to-support-first-class-component-templates/19489
**Category:** Uncategorized
**Created:** [April 9, 2022, 2:29am UTC](https://discuss.emberjs.com/t/getting-addons-ready-to-support-first-class-component-templates/19489 "2022-04-09T02:29:08Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![ef4](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/ef4/32/13470_2.png) [@ef4](https://discuss.emberjs.com/u/ef4)
#### Post date: [April 9, 2022, 2:29am UTC](https://discuss.emberjs.com/t/getting-addons-ready-to-support-first-class-component-templates/19489/1 "2022-04-09T02:29:08Z")

</div>

A public service announcement for addon authors:

[First-class component templates](https://github.com/emberjs/rfcs/blob/master/text/0779-first-class-component-templates.md) is a merged RFC and already has a working implementation. Users are going to want to consume your components from this new style of templates.

Mostly that will Just Work, but there are a few things you may not have considered.

1. **Use component template co-location**. This isn’t just nice for developer ergonomics – it makes components work as first-class values. Without it, your component can’t be passed around as a value in Javascript without losing its template.

2. Make sure the components (and helpers and modifiers) in your `/addon` folder have **reasonable filenames** , because those are going to be what people import from to use them.

First-class templates plus Glint is looking _really_ nice. If you haven’t had a chance to play with it give it a go.

---

_[View the full topic](https://discuss.emberjs.com/t/getting-addons-ready-to-support-first-class-component-templates/19489)._