Code-level access and control
- Stack site owners and their teams do not have direct code-level control.
- Developers can access mirror repositories for local testing.
- Trusted partners can submit merge requests, but these are subject to review and approval by Enterprise Technology Web Services (ET Web).
Custom themes
Webspark transition and subtheme management
After migration, sites with custom subthemes will have their subtheme code included in the stack's codebase. To manage subtheme dependencies moving forward, site owners will need to either:
- Remove dependency on the subtheme so it can be decommissioned
- Request access to the subtheme under the conditions outlined below
Requesting a subtheme
- Requests must be submitted via a Jira Service Desk ticket
- Requests will be evaluated based on the following criteria:
- Demonstrated need where no alternative officially supported solution exists or is planned
- The requesting unit has the resources and skills to maintain the subtheme per the quarterly platform upgrade release schedule
- The subtheme is hosted in an external repository whitelisted in Site Factory by an administrator
- Approval is at the discretion of Enterprise Technology Web Services
Ongoing subtheme maintenance
- The site owner must agree to keep the subtheme updated and compatible with the quarterly upgrade release schedule by providing necessary development resources.
- Requests for subthemes must include a lifecycle management plan and an
Custom modules
There are three options for incorporating custom modules into the platform:
1. Composer package
- Custom modules can be included via the Composer package, but they must pass an ET Web code review before inclusion or upgrade.
- The sponsoring party must:
- Keep the code up to date
- Provide ongoing developer expertise and availability to support updates in alignment with the platform’s upgrade release schedule
2. Pull request (for trusted partners only)
- Custom modules can be added via pull request, but only trusted partners are permitted to submit them.
- The sponsoring party must:
- Keep the code up to date
- Provide ongoing developer expertise to support updates per minor release schedule
3. ASU Enterprise Site (Acquia Cloud Next Platform)
- Sites that fund their own ASU Enterprise Site on Acquia Cloud Next have full code-level access and are not bound by the same restrictions as Stack sites.
Contrib modules (third-party modules)
- Requests for contrib module additions must be submitted via a Jira Service Desk ticket and are subject to review.
- Requests will be evaluated for inclusion in one of the following categories:
- All sites (available platform-wide)
- Limited access (available to specific sites or groups)
Evaluation criteria for contrib modules
A module will be considered for inclusion based on:
- The solution is accessible or can be made accessible with reasonable effort.
- The solution is secure.
- If the module is widely adopted and actively developed, or if abandoned, Enterprise Technology Web must be capable of forking or assuming ownership.
- Dependencies required by the module are minimal and are also evaluated for suitability.
- The module aligns with Drupal trends and platform standards.
- The module does not enforce a strongly opinionated architectural implementation that could restrict future development or updates.
Additional criteria by stack
- Webspark Stack:
- Must meet the general criteria plus:
- Align with ASU Brand Standards.
- Must not introduce functionality contradicting Webspark 2 / Unity Design System architectural vision.
- It must benefit the broader ASU web community.
- Must meet the general criteria plus:
- Enterprise Drupal Stack:
- Evaluated based on the general criteria.
- The College:
- Evaluated based on the general criteria, plus any additional internal requirements from that team
Final approval
Even if all requirements are met, requests may still be rejected if they do not align with the Enterprise Technology Web Platforms team’s goals and leadership decisions.