This project is not covered by Drupal’s security advisory policy.
APEX is the core module of the APEX design system for Drupal. Site builders install it to run APEX Theme and the APEX feature modules; developers use it to build on them.
It holds the shared services every APEX module uses and adds no end-user features of its own. Each feature lives in its own sub-module, so you enable only what your site needs.
Features
The core module provides the shared parts. You see its effect through the sub-modules and APEX Theme.
- APEX menu link: a link under Configuration, at
/admin/config/apex, for people with the "Administer site configuration" permission. - APEX features page: a page at
/apex/featuresthat lists every APEX module, enabled or not, with its category, feature count and state. It needs the "View the APEX features page" permission. Granting it to anonymous visitors tells them which modules the site runs. - Theme and region services: theme detection, region management, and CSS that keeps the APEX layer order.
- Security helpers: an SVG sanitizer and validators for CSS classes, colors, dimensions, keywords and URLs.
- Copy buttons: one shared copy-to-clipboard routine that also works on plain http, with Google Material icons. Every APEX Toast message has copy, move (top or bottom of the screen, kept for the browser tab) and close buttons. Every APEX Form status message has a copy button. APEX Share's Copy link and APEX Blueprint's Copy button use the same routine.
- Layout helpers: breakpoint, fluid scale and resolved width services, plus cache management.
- Drush commands:
apex:install(aliasapex-on),apex:uninstall(aliasapex-off),apex:subthemeandapex:import-blocks. Sub-modules add more:apex:font:listandapex:font:testfrom APEX Font, and a group ofapex:schemes:*commands from APEX Schemes (regenerate, clear, list, enable, disable, delete, validate and test generators). - Integration stylesheets: a YAML entry in
apex.integrations.ymlattaches an APEX stylesheet to a contributed module, and only when both are present.
Sub-modules
The package ships more than 40 sub-modules. Enable them on the Extend page, with a recipe, or with drush apex:install.
- Foundation: APEX Theme Settings, APEX Layout, APEX Width, APEX Schemes (color schemes and their rules), APEX Font, APEX A11y and APEX Performance.
- Design: APEX Color, APEX Color Editor, APEX Region Backgrounds, APEX Style, APEX Typography, APEX Animation, APEX Display, APEX Block, APEX Form, APEX Table, APEX Tabs and APEX Blueprint (a page at
/apex/blueprint). - Navigation and interaction: APEX Menu, APEX Menu Badge, APEX Menu Icon, APEX Off Canvas, APEX Overlay Search, APEX Overlay Login, APEX Toast, APEX Back to Top, APEX Preloader, APEX Social and APEX Share.
- Content: APEX Breadcrumb, APEX Comment, APEX Search, APEX Copyright, APEX Responsive Image and APEX Layout Builder.
- Content widgets and sections: APEX Widgets adds content widgets such as steps, price tiers, quotes and opening hours, and needs Paragraphs. APEX Patterns adds ready-made sections at
/apex/patternsand needs Paragraphs Bundles. - Authoring and AI: APEX Injector for code injection. APEX AI Gateway connects to Claude or OpenAI with your own key and needs nothing outside APEX. APEX AI Bridge routes through the AI module.
APEX Search shows a warning on the status report when Search API is missing, because it then has nothing to style yet.
APEX Theme Test Kit is for development only. Do not enable it on a production site.
Installation: get started in 3 steps
- Install the module with Composer:
composer require drupal/apex - Apply a recipe.
apex-theme-starterinstalls APEX Theme, sets it as the default theme and enables 21 sub-modules.apex-fullenables 38 sub-modules and APEX Theme. Or enable everything that can run on your site with Drush:
drush apex:install - Open "APEX" under Configuration, or visit
/apex/features, and check which modules are on.
drush apex:install skips any module that is hidden, incompatible with your Drupal version or missing a dependency, and names each one it skips. Add --no-theme to keep your current default theme. drush apex:uninstall removes the suite in dependency order.
When you uninstall the suite, drush apex:uninstall switches the default theme, uninstalls APEX Theme, deletes widget content if APEX Widgets is on, uninstalls the sub-modules and removes apex last. Uninstalling APEX Share removes its "Share Buttons" component from saved displays. APEX Theme is listed as required by the theme.
To create a sub-theme, run drush apex:subtheme my_site --label="My Site". It copies the starter inside APEX Theme to themes/custom/my_site and never overwrites an existing folder.
Four sub-modules are in neither recipe: APEX AI Bridge, APEX Widgets, APEX Patterns and APEX Theme Test Kit. Enable them yourself when you need them.
Requirements
- Drupal 11.3 or later, or Drupal 12
- PHP 8.3 or later
The core module needs only the Drupal System module. APEX AI Bridge and one other sub-module, Sub Theme Helper, declare Drupal 11.3 and later only; APEX AI Bridge depends on the AI module, which does not declare Drupal 12. Optional projects: Paragraphs for APEX Widgets, Paragraphs Bundles for APEX Patterns, Key for APEX AI Gateway settings, and AI for APEX AI Bridge.
The recipes were last run on Drupal 11.4.8. On Drupal 12 they have been exercised only in part and are not yet fully verified.
Support and maintenance
Questions, ideas, and bug reports are welcome. Please use this project’s issue queue so discussions and solutions remain available to the Drupal community.
Maintainers monitor issues, but response times depend on availability.

Developed and maintained by Alaa Haddad of Flash Web Center, LLC.
AI disclosure: AI tools assisted with drafting and reviewing this project description. The maintainer verified the final content against the project source.
Project information
Minimally maintained
Maintainers monitor issues, but fast responses are not guaranteed.- Project categories: Content display, Performance, Site structure
- Created by flashwebcenter on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
