It seems that I’ve a very common question. But I’m still thinking about a “out-of-the-box-best-practice”-solution for Document Node lists in the backend. And I need help to clarify it.
Coming from TYPO3 I’m still affected by TCA and simple list management where I can show always the last created items on top and do not have to think about a high amount of datasets in future.
In my actually case I think about how to manage “News”-Documents. I just have a Document Node “News” and under this an unlimited count of Document Nodes which presents single News-Items. But this is not really a good solution. What will happen, if there are one day 10.000 news-items? Will it kill my site?
The most interesting thread I found in relation to this topic is this: Neos for large content webpages
I know I could also write a small Flow-Domain-Model-Extension for this to keep it more simple and get a manageable list. But this is not my intention.
So I’m still thinking about, what the currently best practice NEOS-on-board node-based solution for a common matter like this? For simple news management?
Does I really have to create more folders to take the control about the document tree and an unlimited count of News-Nodes? So I have to create under “/News” the Folder “/2020” to add all news of 2020 there. One year later I create the Folder “/2021” and so on?
a) Is this best solution so far without creating some special stuff?
b) And related to this: Is there any possibility to order the news INSIDE THE TREE by their date? Or by their title? I’ve concerns what happen, if some backend users will do whatever they want. How do I control this, that a Document Node list has a fixed order to avoid some mismanagement and confusion? What can I do, that a single News does not disappear between 200 other news?