Problem/Motivation
The current 8.x port uses config entities for the HTML templates. A co-worker of mine is working on a submodule to this that would use content entities. The advantage of config entities is that they are readily deployable via git (eg, CMI). The disadvantage is they cannot use some of the more advanced features of the content entity system such as bundles (eg, categories of templates), and permissions around CRUD operations.
Proposed resolution
Split the core functionality of this module into a base module (wysiwyg_template_core perhaps), have wysiwyg_template depend on the new module, and then in the near future, add wysiwyg_template_content module that would support templates that are content-entity-based.
Remaining tasks
Review, discuss.
User interface changes
None for now.
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | consider_supporting-2735305-5.patch | 1.23 KB | david.gil |
| #4 | 2735305-04.patch | 9.09 KB | jhedstrom |
Comments
Comment #2
jhedstromNot ready for merge yet, put a proof-of-concept.
Additional functionality that would be common to both config and content based templates:
Comment #4
jhedstromThis additionally moves the interface into the common core module, as it will be used both by the config-based entity, and the content-based entity.
Comment #5
david.gil commentedSend again to test bot
Comment #6
david.gil commentedups sorry last patch no correspond to this issue
Comment #8
jurgenhaasReviewed and pushed to dev