“Atomic content” modelling is an approach that conceives of and stores _pieces_ of content in their smallest, indivisible parts. In this way, they can be rendered in different places and remixed into new articles (https://www.enonic.com/blog/what-is-atomic-content-design).
Imagine a travel feature article that was composed substantially of resort, hiking route and bar profiles, each stored separately and accessible in their own right but pulled into this piece.
It’s widely said that “headless” or “composable” CMSes like Contentful are what really allow for an atomic model, whilst a “monolithic”, traditional CMS like WordPress does not excel in this area.
I’m curious to find examples of deployments where WordPress may indeed have been used to facilitate an atomic content model.
Some rudimentary features are known:
* embed.php could presumably be used to render an included WordPress post.
* Gutenberg uses a “blocks” paradigm, but my understanding is this is rather granular and in-page, ie. blocks for paragraphs etc rather than for whole pieces of distinct content. I’ve frankly never embraced Gutenberg or these modern WordPress features, so I’m not sure what else may be possible.
Has anyone used or seen WordPress used to facilitate this approach?
[ad_2]
Advanced Custom Fields and post meta let you store your content as granular as you like.