Drupal is a registered trademark of Dries Buytaert
Protected Pages 3.0.0 Major update available for module protected_pages (3.0.0). Commerce Core 3.3.8 Minor update available for module commerce (3.3.8). Search API HTML Element Filter 1.0.7 Minor update available for module search_api_html_element_filter (1.0.7). Layout Builder Reorder 2.0.1 Minor update available for module layout_builder_reorder (2.0.1). Ban 1.1.0 Minor update available for module ban (1.1.0). Field Formatter Range 2.0.0 Major update available for module field_formatter_range (2.0.0). Field Formatter Range 8.x-1.8 Minor update available for module field_formatter_range (8.x-1.8). UI Patterns (SDC in Drupal UI) 2.0.18 Minor update available for module ui_patterns (2.0.18). Search API Solr 4.3.11 Module search_api_solr updated after 14 months of inactivity (4.3.11). Provus Mega Menu Module provus_mega_menu crossed 1,000 active installs.

This is a base theme for Drupal, designed to be easily customized and a great starting point for LocalGov Drupal websites. It provides a solid foundation with inline documentation and tools to help maintain CSS coding standards.

LocalGov Drupal Base Theme

Welcome to the LocalGov Drupal base theme.

We developed this theme with scalability, ease of use, and ease of customisation in mind. Making this base theme a great start point for any website using the LocalGov Drupal distribution.

Supported releases

We now have a 2.x and a 1.x branch.

All new feature development work will be against the 2.x branch
The 1.x branch will continue to have bug fixes until the end of December 2025.
Everyone is encouraged to upgrade to the 2.x branch, but please see release notes regarding changes to the grid system layouts, moving from flex to css grids.

https://github.com/localgovdrupal/localgov_base/releases/tag/2.0.0

Inline Documentation

Instead of creating documentation for the theme and storing it in a wiki or something else that is likely to not be updated, we have written detailed comments inline with the code. This should make it easier to know exactly what code block any specific documentation item refers to.

The theme includes an automatically-generated list of all the CSS variables in [variables.md](./variables.md).

Sub-theme

To create a sub-theme, you simply need to run the sub-theme creation script that is in the `/scripts` directory, like so:

  cd web/themes/contrib/localgov_base/
  bash scripts/create_subtheme.sh

You need to enter two items when creating a sub-theme:
1. The name of the theme, this can be anything and can include spaces, e.g. Super Council
2. The machine name for the theme, this must start with a letter and use only lowercase letters and underscores, e.g. super_council

Custom Styles

Hopefully most of the custom styles you will need are set via CSS custom properties in the `/css/base/variables.css` file in your sub-theme.

This is where you set your colours, fonts, spacing, etc. Then you "apply" these variables where needed, like so:

  :root {
    /* Set/Override Variables */
    --color-accent: red;
    --spacing-largest: 5rem;

    /* Apply Variables */
    --color-link: var(--color-accent);
    --breadcrumbs-background-color: var(--color-accent);
    --section-spacing-vertical-header: var(--spacing-largest);
  }

If you need to add any CSS overrides, you can create custom CSS files for these and then a library/libraries to attach them to your components.

Automated CSS Coding Standards

To make sure we follow Drupal's CSS coding standards (without having to think about it), there is a handy `npm` script to automatically scan and fix any CSS coding standards violations.

Simply run `npm install` to get the necessary packages, then run one of the following commands to scan the files and fix any issues.

- "start": "npm run lint:css && npm run lint:js",
- "start:fix": "npm run lint:css:fix && npm run lint:js:fix",
- "lint:css": "stylelint \"**/*.css\"",
- "lint:css:fix": "stylelint \"**/*.css\" --fix",
- "lint:js": "eslint \"**/*.js\"",
- "lint:js:fix": "eslint \"**/*.js\" --fix",

start

This command will run the linter on your CSS and JS files and give you are report in your terminal of any issues. found.

start:fix

This command will do the same as `start` but will also attempt to fix any issues it finds, such as using correct quote marks, fixing indentation, etc.

It's advisable to run `start` after you run this command to see if there was anything the automated linter couldn't fix.

lint:css

This is the same as `start` except it only checks the CSS files.

lint:css:fix

This is the same as `start:fix` except it only affects the CSS files.

lint:js

This is the same as `start` except it only checks the JS files.

lint:js:fix

This is the same as `start:fix` except it only affects the JS files.

Troubleshooting

If you get an error, such as node not being able to find prettier, you might need to install the packages from Drupal core's `package.json`. All of our linting extends Drupal core's linting to make sure we are always following Drupal's exact coding standards. To do so, simply `cd web/core` and then `npm install`.

If you still cannot run the linter, make sure you are using the correct version of Node. We have a `.nvmrc` file to help you. Run `nvm use` from your theme directory to install the correct version.

Activity

Total releases
24
First release
May 2025
Latest release
1 month ago
Releases (12 mo)
19 ▲ from 5
Maintenance
Active

Release Timeline

Releases

Version Type Release date
2.5.1 Stable Jun 9, 2026
2.5.0 Stable May 19, 2026
1.10.1 Stable May 19, 2026
1.x-dev Dev May 18, 2026
2.4.0 Stable May 7, 2026
2.3.4 Stable Mar 16, 2026
2.3.3 Stable Jan 27, 2026
2.3.2 Stable Jan 6, 2026
2.3.1 Stable Dec 10, 2025
2.x-dev Dev Dec 5, 2025
2.3.0 Stable Dec 1, 2025
1.9.2 Stable Nov 19, 2025
2.2.5 Stable Nov 19, 2025
2.2.4 Stable Nov 19, 2025
2.2.3 Stable Nov 19, 2025
2.2.2 Stable Nov 19, 2025
2.2.1 Stable Nov 19, 2025
2.2.0 Stable Sep 4, 2025
2.1.2 Stable Sep 4, 2025
2.1.1 Stable Jul 17, 2025
2.1.0 Stable Jul 17, 2025
1.9.1 Stable Jul 17, 2025
2.0.0 Stable Jul 17, 2025
1.8.11 Stable May 1, 2025