What structure should the extensible data have?

Question

Programming

For example, there are several hundred modules, sorted and arranged into folders according to their point of application (tachi, desktops, etc.).
Each of these modules also has a number of explicit attributes. For example, belonging to the header or footer of the page. But sorting by these attributes is performed by external means and the folder structure itself remains unchanged.
Attaches an example(s) of its application to each module.
What method of building a folder tree should be used so that another 300 modules that appear in six months do not kill the ability to see the big picture?

Answer 1

Are you talking about CMS? About what? You somewhere lost the introductory part of the question.