Taking over the Sites namespace

Current situation

The "Sites" module last active development happened 10 Years ago. The last real issue has been opened about 7 years ago with no reply of one of the maintainers. Despite the reports showing that there are still 30 sites around using this module, the usage numbers are constantly dropping.

Also there has been no efforts to make a D8+ version of this module at any point. Which leads to the conclusion that the namespace for D8+ projects is theoretically free.

Motivation

I created a module on a clients project, which resolves similar needs than this module did. It provides a multisite solution based on a single database, but with certain settings different across sites - which is exactly what the Site modules project scope once was. In comparison to the popular "Domain" module, the architecture does not rely on config but on a plugin system which allows a long range of development-oriented possibles to implement custom business logic determine which content belongs to which site.

Belong the different technical approach, it comes with a virility of useful integrations and submodules to extend those features or make them through a UI accessible for site builders.

I strongly want to share my solutions with the community, to provide an alternative approach for multisite handling with a single database. I believe that there is a need, since the Sites module already has been used in the past, but also because I see a rising demand for multisite and microsite solutions.

I believe that the Sites namespace best fits for that contribution.

Owner contacted

I contacted the owner before I opened this issue via the contact tab on his user profile.
The mail has been sent to brynbellomy on the 12. February 2024.