Possibility to create templates on different environments

[LarsDol]

What would you like to see added to or changed in Content Templates, and why?

Hi!

We're trying out the content-templates plugin, which looks very promising already!

One thing that's a bit limiting at the moment is that templates are always stored inside the project config. We're in a situation where we would like our client to create these templates themselves, or at least be able to edit them.

Some ideas that may work in our situation:

• Let the developers configure which templates exist (as is now), but allow the content to be overwritten and saved on each separate environment (by certain user roles).
• This may be a (Boolean) setting when creating the template. Something like "Synchronise content on different environments". If it's true, use the current behavior. If false, use the behaviour as suggested above.
• Add an import / export function of templates to allow for a solid starting point (without losing the flexibility of changing the templates on different environments).

It would also solve the issue where it's not possible to add relations to assets and other entries in templates. Not sure if this is technically feasible, but it would greatly help out for any of our projects. The plugin would be a real improvement in the editorial flow of our clients!

Keep up the good work!

Greetings,
Lars Dol

Front-end lead @ Digital Natives Amsterdam

[ttempleton]

I'm not sure we'd be able to have a per-template setting, since the order of templates is also stored in the project config. I definitely understand that there may be cases where you want clients to create templates for their content editors to use, though. Maybe we could have a global plugin setting for using the project config vs. allowing creating/editing in different environments.

[LarsDol]

Cool, I think a global setting would suffice for us! The scenario you subscribed is exactly the one we're about to run into. If it's possible to add a feature like this, that would certainly mean we'll use the plugin. Probably for many more of our clients as well! ✌️