Sub-Theme inheritance
Last updated on
1 June 2025
This documentation needs review. See "Help improve this page" in the sidebar.
In the previous section, We understood how sub-theme is created along with inheritance of various properties.
The list below summarizes the inheritance properties:
| Property | Inherited | Notes |
|---|---|---|
| CSS | Yes | |
| JS | Yes | |
| Templates | Yes | |
| Screenshot | Yes | |
| Block placement | Yes | Only if the sub-theme does not supply any blocks of its own, and other requirements. See Inheriting Block Placement. |
| Block templates | Yes | With extra steps required. See Inheriting Block Templates. |
| CKEditor Stylesheets | Yes | Overriding this from the sub-theme requires extra steps. See Allow overriding/disabling base theme's ckeditor5-stylesheets value. |
| Theme Settings | Yes | |
| Breakpoints (via themename.breakpoints.yml) | Yes | |
| Libraries (via themename.libraries.yml) | Yes | |
| Features | No | |
| Logo | No | |
| Favicon | No | |
| Regions | No | See Inheriting Theme Regions. |
| Color module support | No | |
| Core Version | No |
Help improve this page
Page status: Needs review
You can:
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion
Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.