The core distribution will always strive to be:
- As minimal as possible on top of Drupal Core providing performance, scalability, and security features on top of it
- Provide best practices for users to follow which includes our Composer workflow, CI / CD methodologies, and deployment strategies
- Provide a place for all Government Departments to inherit the base requirements such as Language Handling, GC Approved Themes, and other functionalities such as Date Format, Metadata Output, and Accessibility improvements
Beyond the above the distribution will provide extensible features that can be opted into through the wxt_ext suite of modules:
- Each of these modules must explicitly state all of there contributed dependencies
- Governance around these “extension” modules can be a bit looser
- These modules should be clear in focus and not try to do to much other then an immediate task at hand
- These modules should have an
modulename.wxt_extension.ymlfile so can be enabled as optional extension during profile installation
In addition, Drupal WxT will offer out of tree (external) modules that implement specific features:
- These features are not included by the core platform because they are only used by a subset of users
- These modules may be subject to change though update hooks will always be provided
- Community supported modules will also be listed in our README of additional modules but will not be supported by the Drupal WxT team
Note: The governance around the core distribution will always be much stricter then the governance around adding a
wxt_extor an out of tree module.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.