Reusable Components

[scottnash]

Allow the creation of a component where the instance of that component can live on multiple pages and edited in one place that will update the component everywhere it is located. Unlike bookmarks, which are copies of the same component, this would literally be the same component.

"having a specific instance of say sponsored-header on all articles created with a particular template"

"the use case would be especially relevant for components that can't live at the layout level, say in-article components like the newsletter signup where we want to be able to update the logic and have it apply in multiple places. Bookmarks solve for manually added components, but we can't always expect editors to be controlling that placement"

Where would the component be edited? Editable from every page, or should there be a separate place to edit these types of components and they can only be added or removed on the page?

[ncbooth]

We currently have several components in the layout that we use like this. As a result we've had to give admin accounts to all of our editors. I think it would make sense to indicate a component is global, but allow it to be edited anywhere that it is included.

This would also vastly simplify our layouts, which right now require an odd setups to keep some components article-specific and some global.