Thanks for the thorough explanation John!
For the loader you brought up, this means on my dev version I add say 3 new layouts and get the JSON file for that Flexible Content, I can then put that JSON file into the client’s JSON folder (which would be a child theme of my premium theme) and the loader will ignore all the existing field_names and add only the new layouts? Please confirm, as I would hate for their values they saved to be replaced with my dev values.
Lastly, on the template inquiry. To make sure I stated it right. I was hoping to have a way that I can easily populate the ACF Flexible Content fields of a page from an example I have already done. Therefore, have layouts already completed in the order and values I pre-determined. This is merely to save me or them from having to select the layouts and values to match my example page.
