Goal
Dotkernel Light is designed to be a fast-start example of using the Mezzio microframework, as well as an entry-level version of Dotkernel Frontend. Its purpose is to present the newbie developer with as few moving parts as possible, while also giving the more advanced developer a starting point with full control of the platform's functionality.
Light retains the modern architecture of Mezzio microframework and several Laminas components used in Dotkernel Frontend. The low number of out-of-the-box components encourages active exploration of the functionality required by your application - you add only the packages your application needs.
Components and functionality
Dotkernel Light is a stripped-down version of Dotkernel Frontend. Like Frontend, it is built on top of Mezzio microframework using Laminas components, but with limited features and a lower number of packages, which makes the learning curve of working with the repo considerably gentler.
Functionality retained
- Routing
- Templating
- Error handling
- Tests and code quality checks
Items removed compared to Frontend
- Doctrine and all database-related stuff
- Sessions/Cookies/Flash messages
- Authentication/Authorization
- Dependency Injection
- Mail-related stuff
- Navigation
- CORS
- Forms/Validators/InputFilters
- User module
- Contact module
- Plugin module
- CSS/JS code no longer in use due to the above module removals
- Instructions from README.md that are no longer needed
Packages no longer required
- dotkernel/dot-authorization
- dotkernel/dot-data-fixtures
- dotkernel/dot-dependency-injection
- dotkernel/dot-flashmessenger
- dotkernel/dot-mail
- dotkernel/dot-navigation
- dotkernel/dot-rbac-guard
- dotkernel/dot-response-header
- dotkernel/dot-session
- laminas/laminas-form
- laminas/laminas-i18n
- mezzio/mezzio-authorization-rbac
- mezzio/mezzio-cors
- ramsey/uuid-doctrine
- roave/psr-container-doctrine
- mezzio/mezzio-tooling
- rector/rector
Frequently Asked Questions
What is Dotkernel Light? +
Dotkernel Light is a version of Dotkernel Frontend that includes only the bare-bones essentials. It's suitable as a presentation site, an introduction to the Mezzio microframework architecture, or a starting point for a more complex project where you want full control over functionality.
What is the goal of Dotkernel Light? +
It's designed to be a fast-start example of using the Mezzio microframework as well as an entry-level version of Dotkernel Frontend, presenting the beginner developer with as few moving parts as possible while still letting the more advanced developer have full control of the platform's functionality.
What functionality does Dotkernel Light retain? +
It keeps routing, templating, error handling, and tests and code quality checks.
What was removed compared to Dotkernel Frontend? +
Items removed include Doctrine and all database related stuff, sessions/cookies/flash messages, authentication/authorization, dependency injection, mail related stuff, navigation, CORS, forms/validators/input filters, the User module, the Contact module, the Plugin module, unused CSS/JS code, and outdated README instructions.
Which packages are no longer required in Dotkernel Light? +
Packages such as dotkernel/dot-authorization, dotkernel/dot-mail, dotkernel/dot-session, dotkernel/dot-navigation, dotkernel/dot-flashmessenger, laminas/laminas-form, mezzio/mezzio-cors, and several others used by Frontend are not required.