When we build a rich content field, we're thinking that we'll need multiple channels to transmit its data, e.g.
a content channel with HTML value, like <p>Lorem ipsum <data-embed-field=as7refg"> blah.</p>
a fields channel with straight-up structured field data, like {"as7refg" => {"image_id" => 123}}
This will let us have a really powerful WYSIWYG editor with arbitrarily complex embedded data, since that can go into the fields channel and doesn't have to be awkwardly jammed into HTML data attributes.
For this to work, we'll want to support fields that can map to more than one channel of data, not just a single value.
When we build a rich content field, we're thinking that we'll need multiple channels to transmit its data, e.g.
contentchannel with HTML value, like<p>Lorem ipsum <data-embed-field=as7refg"> blah.</p>fieldschannel with straight-up structured field data, like{"as7refg" => {"image_id" => 123}}This will let us have a really powerful WYSIWYG editor with arbitrarily complex embedded data, since that can go into the
fieldschannel and doesn't have to be awkwardly jammed into HTML data attributes.For this to work, we'll want to support fields that can map to more than one channel of data, not just a single value.