Skip to content

Config Pages and Drupal 11

Ready

The latest stable release, 4.0.1, declares a core version requirement of ^10 || ^11 || ^12, which covers Drupal 11.

DO I NEED IT? Tired of building custom forms with FormBase just to create admin settings pages? Fed up with writing controllers and routing YAML files for simple configuration interfaces? Frustrated with creating single-use content types for homepage settings and then explaining to clients why they can only create one node of that type? And don't get me started on what happens when clients want

Key facts

Project
config_pages
Latest stable with Drupal 11 support
4.0.1 (9 Aug 2026)
Core version requirement
^10 || ^11 || ^12
Maintenance status
Actively maintained
Reported installs
21,661
Last synced from drupal.org
21 Sept 2026

Every field above comes from the drupal.org API. The Drupal 11 status is derived from the core version requirement across this project's releases.

Source: drupal.org/project/config_pages