#Working With Rich Text Embeds
Recently, we announced the ability to embed assets into the Rich Text Field, allowing content operators the ability to easily reference images and other assets within their content entries. We've further expanded this functionality to give users the flexibility to embed several new and different types of entries, either as a block, or an inline element.
Our focus was to give control and flexibility back to the creator to add information, assets, and important links into the text as needed while reducing clutter and enhancing content for your intended audience.
A block embed is a chunk of information that sits between the text. This is a great way to add in content items like assets directly into the content entry to help visualize an idea, for marketing campaigns with visual elements, or help eCommerce Managers and Content Creators amplify a product catalog by embedding product callouts with information like images, links, pricing, stock and more.
As the name implies, inline embeds allow Content Creators to link to external content or items directly inline with the text. An example of a powerful use case for inline would be in the case of attribution where Creators need to accredit authors for quotes, blogs or other types of articles. There have also been cases of linking to citations, titles, or legal copy.
Rich Text Embeds also allow for more information without added clutter in the Content Model, and ensure that Content Creators have maximum flexibility without their dev teams needing to build out single-use Content Models in the Schema Builder. All models can be embedded into the Rich Text Field Type via a configuration setting. On the API side, we create a union relation that references the selected model.
With Rich Text Embeds enabled, your API will have some new types added. The name of your field will now be a type appended by RichText, and RichTextEmbeddedTypes inside your Schema.
Blog Author