New CMS

General
,
1

I tried the new CMS and I’d like to understand it better.

I get it, adding a new “structure” creates an object definition in the backend and the editor allows me to add new objects of that type. I really like the idea, makes total sense to use Objects.

But how is the content supposed to be rendered? Display pages only? What if I want to show several of them on a page like classic Webcontent? Add a fragment using restUtil to fetch the content? Is there maybe a trick?

Also: I noticed, that I can see the Author in the json through the API (when I set it to public, everybody can read it). But the meta data should NEVER be available to the public. It would probably be fine and even a feature in an Intranet, but in an Internet website?

With webcontent or fragments this was never a problem since they are rendered using Freemarker and the actual backend data was never exposed.

What is the idea/plan here?

Thanks, Christoph

Thanks for the feedback Christoph, as it was mentioned, you should map the same way you do with the current web content on a page. The point about the metadata exposed on the API will be solved with headless capabilities that are coming to allow you to configure the JSON you want to expose. This is right now under discovery by our team.

 –

1 Answer

1
2

Hi Christoph,

Good to see you again!

I also did some testing, and as far as I understand, the rendering will be more or less the same as with the regular Web Content, by mapping object fields to fragment fields. Full content should be rendered on the Display page, Collections using Collection Display Fragments, and the last resort is always mapping a fragment field to a field of a specific object. All with OOTB features, no freemarker or restUtil.

What I don’t know, though, is how we’re going to display multiple articles of different structures in the same Collection. For example, all the structures may share a common section (Teaser), and Common collections (e.g. Latest Updates, which might show all types of content like News, Events, Stories, Press Releases, etc.) should handle the structure-field-to-fragment-field mapping only for the Teaser section.

Best,

KG

Hi Krzysztof, I am often lurking, but rarely writing. Anyway, I believe, what I am actually looking for is basically a feature that doesn't seem to exist yet. Predefined a template (fragment with mapping, whatever) and simply drag & drop a cms article/object to a page. Display pages are fine for "full articles" but what if I want a simple webcontent that is shown on multiple pages? Your usecase is also very valid, I have exactly the same usecase here. I also have Press Releases, events, ... based on the same type "Teaser" (same name!). Very good question how to solve it.

 –

Hmm, we are using a similar feature in the current CMS. One of the available fragment configuration fields is an Item Selector (https://learn.liferay.com/w/dxp/development/developing-page-fragments/reference/fragment-configuration-types-reference#item-selector-configuration). It means you can drop a fragment on a page, then select an article, and the fragment (written in freemarker) automatically adapts to what is in the Article. I'm not sure, though, if you can select the new CMS Objects in the same way, and how it will handle the potential common Teaser sections.

 –