- Issue created by @mandclu
- 🇨🇦Canada mandclu
Another potential approach would be allowing the module to define profile/templates, and then those could either be associated to bundles (similar to workflows) or potentially specified as part of the token.
- 🇨🇦Canada mandclu
The more I think about this, the more I think that profiles as configuration entities is the best approach. In particular, these could be fieldable entities, which could be an easy way to address issues like ✨ Allow for a foreground image element Active , and then using this module with something like Field Token Value → would open up all kinds of possibilities. I'm not sure if it would be possible to integrate with Field Group as a way to allow for simple layout options, but it would be worth exploring.