/
Separating 'core' module from 'kernel'
Separating 'core' module from 'kernel'
Average In-Portal installation consists of following folders:
- admin - system presets and index.php file to allow access to Admin Console by going to /admin/ url
- core - all In-Portal's Admin UI plus
- core/kernel - core PHP classes that allows In-Portal to operate (e.g. event handling code, template parser, etc.)
- modules - each sub-folder is a specific module
- themes - each sub-folder is a Front-End theme
- tools - misc command-line tools
Based on this we have a problem, because "core" folder is a module from one side and should be located under "modules/core" folder instead, but it's also a kernel, that can work without "core" module itself.
I'm proposing to:
- move "core/kernel" folder to "kernel"
- move "core" folder to "modules/core"