Custom datatype for Content Fragments Model (cfm) in AEM to generate auto-generated ID | AEM Community Blog Seeding

[#1]

Custom datatype for Content Fragments Model (cfm) in AEM to generate auto-generated ID by Ankur Garg

Abstract

With rise of omnichannel, the necessity of managing content for multiple touchpoints has complicated the content creation process for business.
Structured Content Fragments were introduced in AEM 6.4 and allow an author to define a data schema, known as a Content Fragment Model.
Content Fragments, independent of layout, can be used directly in AEM Sites with Core Components or can be delivered in a headless manner to downstream channels for omnichannel.
Content fragments allow you to:
Consider how to reach target audiences efficiently across channels.
Create and manage channel-neutral editorial content.
Build content pools for a range of channels.
Design content variations for specific channels.
Add images to your text by inserting assets (mixed-media fragments).

They are channel-agnostic, which means you can prepare content for various touchpoints.
Various data types are available out-of-the-box, including single-line text, multi-line rich text, numerical fields, boolean selectors, dropdown menu options, date and time, and others.
For majority of the use cases, the given content fragment datatypes will satisfy any use cases even the multi-level hierarchy. But still if there is a case where out-of-box datatype can not handle the scenarios, it’s easy to create custom datatype.

Read Full Blog

Custom datatype for Content Fragments Model (cfm) in AEM to generate auto-generated ID

Q&A

Please use this thread to ask the related questions.