Make it possible for Project Browser to activate different kinds of projects

Looking at this Draft MR today with @phenaproxima - https://drupal.slack.com/archives/C01UHB4QG12/p1715785363763219

This feels like the right general approach to me, we need to abstract 'activation' from assumptions about project type so that we can support more things. This is how I would have approached it, also.

General considerations are namespace collisions - but sounds like using Project (which already knows its type) will handle, for example, a recipe named 'zen' and a module named 'zen' - should such a thing exist.

This gives a good separation of concerns, also, that Projects can be meta/global information about a project from the source, and Activators can store more site-specific information relative to this Project - i.e. "installed status" for a Project.

Is it possible to have a story in the OP? I kinda follow but it's easy to misinterpret stuff for those coming in blind since DrupalCon.

This is now hard-blocked by #345165: Click the submit button in the ACP takes me to Website could display the page → .

I was searching for themes when I stumbled upon this issue. I'm really hoping it will support themes, which would be a fantastic bonus.

Thanks!

Theme support isn't going to be added by this issue, but this will lay some of the groundwork needed in order to support themes. :)

@phenaproxima

Yes, I agree. :)

Blocker's in!

Manually tested this on my local machine, by the way, and it worked flawlessly.

chrisfromredfin → credited bnjmnm → .

One giant leap for mankind...

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