On the other hand, OptionTree also hold all data in one field, and from time to time I have a buyer who have problem with saving all options because of that.
When having a composer, isn’t it better to have it saved in the post or page meta itself, so that when viewing a post or page, you don’t have to make another call to a database table or other custom post type?
Isn’t that faster or doesn’t it matter real much?
I’ve seen that plugin visual composer in action, and that one saves everything by putting it inside the main editor content through shortcodes etc. But i really don’t like that since you have a real shortcode mania mess in your editor that way.
So i’m at the choise: post meta or custom table. I can see the benefit of both though, just can’t make a decision
Of course you will save the layout of the post in it’s post meta.
What I suggested was related to custom layouts. I believe you have noticed how some visual composers offer you to store the often used layouts for the later use. I was suggesting that the layouts themselves could be stored each as a custom post type, just because it’s always better to stick to the tables you have if you can, rather than creating new ones.
The fieldtype where WP stores Meta Value is Longtext and maximum size of an entry is “4,294,967,295” bytes.
So if your data is lower than 4GB(Which i think it will) than your good to go.
But to be sure just check the way how Wordpress handles Queries based on Meta Key and Meta Value if you have any case.