Right now, Project Browser can only work with one kind of Drupal extension: modules. It only knows how to enable those, and has certain hard-coded assumptions around that.
But since recipes will be a thing too, wouldn't it be amazing if you could use Project Browser to find and apply recipes? We think so.
The good news is that Project Browser is not, as far as I can tell, too far off from being able to do this. The bad news is that recipe discoverability -- that is, finding recipes on drupal.org or some other repository -- might still be a ways off, since recipes are not a recognized project type on drupal.org yet, and it's unclear what blockers might exist to making that happen.
Therefore, let's be clear on the scope here: this meta is about making Project Browser install recipes which are already installed locally -- which is to say, recipes which are already present in the project's recipes directory.
Within that scope, there are some distinct issues:
I'll add more issues there as they arise.
Meanwhile, here's what's been fixed:
Fixed
1.0
Code
A potential blocker for Drupal Starshot. More information: http://www.drupal.org/project/starshot
📌 Activators should be responsible for generating project commands Fixed is in, so that just leaves ✨ Create a source plugin that exposes recipes in the file system Active .
Since that latter issue will make local recipes fully supported, I think we can call this meta done.
Automatically closed - issue fixed for 2 weeks with no activity.