Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,059 of 9,059 pages
About the help in other languages
All help pages

admin4 module stylesheets

Where CSS goes when the shared components are not enough: the kernel's module stylesheets (setup, content, people, structure, workflow, help) loaded through AdminComponentCSSFileList, and an extension's own admin…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/designers/theme-design/admin4-module-stylesheets.md

On this page

admin4 module stylesheets

This page is for designers and developers who need CSS for an admin page that the admin4 components cannot express. It answers: which file it goes in, how that file is loaded, and how to name the classes.

Contents

  1. Kernel pages: the module stylesheets
  2. Extension pages: your own stylesheet
  3. Rules for the CSS itself
  4. After a change

Kernel pages: the module stylesheets

The kernel's admin pages share one bundle. settings/design.ini [StylesheetSettings] AdminComponentCSSFileList[] lists:

AdminComponentCSSFileList[]=components.css
AdminComponentCSSFileList[]=modules/setup.css
AdminComponentCSSFileList[]=modules/content.css
AdminComponentCSSFileList[]=modules/people.css
AdminComponentCSSFileList[]=modules/structure.css
AdminComponentCSSFileList[]=modules/workflow.css
AdminComponentCSSFileList[]=modules/help.css
FileFor the modules
modules/setup.csssetup
modules/content.csscontent
modules/people.cssrole, section, state, user, notification, collaboration
modules/structure.cssclass, pdf, rss, package
modules/workflow.cssworkflow, trigger, audit, shop, settings, infocollector, search, url, visual, contentfinder
modules/help.cssthe help pages

Each exists in design/admin4/stylesheets/modules/ and design/admin/stylesheets/modules/. admin4's page_head_style.tpl loads the list after the design's own stylesheets and before BackendCSSFileList.

Extension pages: your own stylesheet

An extension does not add to AdminComponentCSSFileList. It keeps its stylesheet in its own admin design folder and adds it to BackendCSSFileList[]:

# extension/myext/settings/design.ini.append.php
<?php /* #?ini charset="utf-8"?
[ExtensionSettings]
DesignExtensions[]=myext

[StylesheetSettings]
BackendCSSFileList[]=myext-admin.css
*/ ?>
extension/myext/design/admin4/stylesheets/myext-admin.css

It loads after the components, so the extension has the last word on its own markup. See Tutorial: add an admin module stylesheet.

Rules for the CSS itself

  • Only what the components cannot do.
  • Class names .a4-<module>-* for the kernel's module files; an extension uses one prefix of its own.
  • Only tokens for colors, radius, spacing, fonts and z-index; no hard-coded values (the test checks the module files).
  • A dark value for every color token you add; normally you add none.
  • Logical properties (margin-inline-start), so right-to-left works.

After a change

Deploy with the packer step (./console exp:velocity deploy --packer), which clears the template-block cache that holds the packed link, and hard-reload. Check the page light and dark, at 1440 px and at 960 px with scale 2.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x