This set of Feature Packs delivers updates to Content Fragments, the JSON Exporter and Core Components.

These enable the definition of structured content for the fragments; together with the updated JSON
exporter, this structured content can then be used to deliver AEM content via
Content Services to channels other than AEM pages.

Visual assets inserted into the fragment itself are attached to the preceding paragraph in the fragment. This means that you cannot position in-between content between a visual asset and the preceding paragraph.

Caution:

After you have added in-between content to a content fragment on your page, then changing the structure of the underlying content fragment (i.e. in the content fragment editor) could lead to erroneous/unexpected results.

When this occurs the in-between content is kept as is:

In-between components have an absolute position within the sequence of components in the fragment flow. This position does not change, even when the content of paragraphs in the fragment changes.
This can make it appear as if the relative positioning has changed, as in-between paragraphs have no contextual relationship to the (fragment) paragraphs they are positioned next to.

Unless the two paragraph structures conflict; in such a case, the in-between content is not displayed (although it is still present internally).