Content Repository for the CMS!?

[SuperFlySly]

I am enthusiastic about Pimcore and I think Pimcore is one of the best open source projects. However, in my opinion, what is urgently needed is a content repository for the CMS area. This feature would make Pimcore even more powerful and flexible than it already is. It would also solve a lot of problems, especially when it comes to updates or reusing content for different areas.

CMS systems that already stand out by providing a content repository are for example the Neos-CMS or the Sulu-CMS.

A content repository would make Pimcore a real game changer.

What do you think?

[kingjia90]

Thank you for your feedback!

Out of personal curiosity, what is a Content Repository? How would it differ from the Assets + Direct Edit? Isn't the same thing at some degrees?

[SuperFlySly]

Hi, you can find out what a content repo is here

https://en.m.wikipedia.org/wiki/Content_repository

and in my opinion the best and most advanced content repo implementation is Neos Content Repository: https://docs.neos.io/guide/content-repository/data-structure

especially because of the Concept of „Content Dimensions“.

[fashxp]

But why not use data objects when you need the things described above, and use documents when you need more fexibility and freedom? And combine the things where needed...

[twin-elements]

@SuperFlySly Do I understand correctly that your main concern is searching through documents?

[dpfaffenbauer]

@SuperFlySly Neos Content Repository is also unstructured, quote:

The content in Neos is not stored inside tables of a relational database, but inside a tree-based structure: the so-called Neos Content Repository.
To a certain extent, it is comparable to files in a file-system: They are also structured as a tree, and are identified uniquely by the complete path towards the file.

Similar to Pimcore Documents, you have the FullPath, and then the path to the editable.

[SuperFlySly]

Ok guys, I would like to use content inheritance and would love it if I could use Pimcore out-of-box as a headless CMS, until then I have to fall back on the Sulu CMS.

[dpfaffenbauer]

Content Inheritance is supported. Headless as well. Headless is just JSON rendering instead of HTML ;). Install dachcom toolbox that has headless support out of the box.