platformOS Core Module
The goal of the platformOS Core module is to extend the platformOS module system's possibilities.
With the hook system, it's possible to use SOLID's Open/Closed Principle so you can modify the business logic in other modules in the application folder without changing the source of existing modules.
There is a variable storage that can be used to set variables and get their value in the global scope.
You can register your module and theme into the module registry with
hook_module_info. In this info file, you can define your module's name, version, type (module or theme), and dependencies. Module registry will handle dependency management and outdated versions.
There are module helper functions to check if a module or theme exists in the system, so that the other modules can use installed ones without hard dependencies.
The modules described in the platformOS Kits section are still in active development. We are working in the GitHub repositories of the modules, where we frequently update the code and documentation. The platformOS Standards are a community effort, and we'd love to get your input. We invite you to contribute to the development of the modules by sending us your feedback, having a conversation on tickets, or opening a PR with code or documentation adjustments on GitHub:GitHub repository of the platformOS Core Module