• 2.x vs 3.x architecture -- the legacy flat naming (domain.config.{id}.{name}) vs native config collections (domain.{id} collection with original config names)
  • Limitations of the 2.x approach -- namespace pollution, fragile regex parsing, no core API integration, broken export/import
  • 3.x benefits -- clean separation, standard ConfigFactoryOverrideInterface, proper export/import with subdirectories
  • Runtime override resolution -- the two-layer cascade (domain-only at priority -253, then domain+language at -252) with a concrete system.site example
  • Domain context -- how DomainNegotiationContext drives override selection
  • Caching -- cache suffix and domain cache context
  • Config lifecycle events -- save/delete/rename propagation to domain collections
  • Config export/import -- directory structure for sync and module defaults
  • Domain Config UI integration -- link to the existing docs
  • 2.x to 3.x migration -- the 5-step DomainConfigMigration service and update hook
  • Services reference table

Issue fork domain-3574966

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mably created an issue. See original summary.

mably opened merge request !320

  • mably committed 86193850 on 3.x 
    task: #3574966 Add a documentation page about the domain_config module...
mably’s picture

mably commented
Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.