Creation of personal CMS classes and libraries

I am building my personal CMS and need your advice on organizing core functions and classes. I have folders:

/shared
   /classes
       DB.php
       Session.php
       Config.php
       ...
   /libraries
       Arrays.php
       DateTime.php
       Email.php
       ...

The files in the "classes" folder contain the main classes (one class for each file).

Now we are talking about / libraries / - they contain functions that can be used in any class, and sometimes they use some other function from another library, and sometimes they need to access some base class. Should I just write them as functions, or make them static and wrap them in some kind of class? Mostly I need them everywhere, but I keep them organized.

+3
source share
2

- CMS. , 100% , , , , , , .

, . , , , . .

, ( , MVC, HMVC PAC), , [/core], [/libraries], [/].

. , .. [/core] [/], [/models] [/core].

, , . , . , , - .

0

, ? , .

? , , .

+1

All Articles