Many newcomers to the CMS market use a fully “content based” model. This means that instead of editing pages, the author edits a single piece of content. Like a product or vacancy. The whole idea behind this is to allow for maximal content re-use, even across channels.
From an architectural perspective, this is a great idea, however there is a downside. The authoring experience is not always optimal. Mainly because the context of the content is missing. It's not always clear where or how the content is utilized. Perhaps it’s too long or too short, or doesn’t fit the context well.
AEM offers a hybrid approach. It has always been a possibility to use page-based editing (an author is editing a page that looks like what the visitor would see). However, there is also the possibility to create centrally managed content fragments that are part of a structure. These fragments can be exposed individually or used on a page if and when desired.
A New GraphQL-based API is the latest addition made to the products in 2022 is, making it effortless to re-use content fragments on any platform. By modifying the query sent to the API, the consumer has full control of the data returned, and can request exactly what is required.
Allowing this kind of flexibility offers the best of both worlds – maximum content re-use by working with fragments, but also user-friendly “in context” page editing simplicity.