Imagine a very simple blog. Blog posts are just a title and a paragraph or three. In that case, having a CMS where you enter the title and those paragraphs and hit publish is perfect. Perhaps some metadata like the date and author come along for the ride. I’m gonna stick my neck out here and say that title-and-content fields only is a CMS anti-pattern. It’s powerful in its flexibility but causes long-term pain in lack of control through abstraction. Let’s not have a conversation about CMS’s as a whole though, let’s scope this down to just that content area issue.
Now imagine we have a site with a bit more variety. We’re trying to use our CMS to build all sorts of pages. Perhaps some of it is bloggish. Some of it more like landing pages. These pages are constructed from chunks of text but also different components. Maps! Sliders! Advertising! Pull quotes!
Here are four different examples, so you can see exactly what I mean:
I bet that kind of thing looks familiar.
You can absolutely pull this off by putting all those blocks into a single content field. Hey, it’s just HTML! Put the HTML you need for all these blocks right into that content field and it’ll do what you want.
There’s a couple
Source: https://managewp.org/articles/16224/how-different-cms-s-handle-content-blocks-like-wordpress-gutenblocks
source https://williechiu40.wordpress.com/2017/10/01/how-different-cmss-handle-content-blocks-like-wordpress-gutenblocks/
No comments:
Post a Comment