Ideas

Allow having field templates created and maintained as classes in code, should work the same for all objects (page/product/media etc.).

Attributes of the class would be fields in the template, similar to the functionality in Litium pagetypes before version 7.

Changes to the template in backoffice could still be allowed but it should be clear in the UI what the differences are between code and db versions of the template. It should also be possible to revert any db changes to the coded version again.