Give the developer the ability to split the content into multiple files. Thus content.txt can be split into several files, one form of which could be :
This optional division gives the developer the possibility to segment his content. For example, a file for the editorial content, another for the representation (i.e. CSS code)…
This could give:
Warning, this is a proposal of formalism for the illustration of my point and not an actual technical solution.
Another very important advantage is to secure data by placing them in a separate file.
This idea came to me with the implementation of the UUID in version 3.8 which poses a major problem of data segmentation. The UUID is indeed a reference and as such should not be edited directly by the user. In the current implementation, this UUID is placed directly in the content file which can be modified by the user. While the Panel can secure this, there is no protection against manual editing of the file by an editor.