It appears this module may be attempting similar functionality as the custom_field → module that I'm actively maintaining. I've built a service that can be utilized in update hooks to add/remove columns → and have advanced display modes to make form layout quite easy. These features among several more I believe make my module a viable alternative to traditional field api content modeling where every field is a table. In many cases custom_field can replace paragraphs/blocks which substantially enhances performance and scalability for larger sites.
If the maintainers of this project are still interested in this 'composed' field content modeling idea, I'd encourage to mark this module obsolete and consider joining efforts in making custom_field even better. Feel free to reach out if you have any questions or insight. Thanks!
Closed: won't fix
1.0
Miscellaneous
Thanks for reaching out.
Whilst the two modules are trying to solve the same problem, their implementations are very different.
I'm trying to make mine generic so it works with any existing field type, whereas custom field is supporting a fixed set of field types.
Congrats on getting it to a working state, looks amazing.