Support "non-traditional" project types

Note that this is a follow up from Slack conversations.

Thanks for creating.

I don’t have strong opinions on this. Mainly it would be great to be able to categorize and search all recipes or agents or prompts easily.

Recipes use General Projects on Drupal.org, and are discoverable using it's composer type. Are your AI agents, and prompts types going to be composer packages? If so, the same workflow could happen as recipes.

Adding additional content types adds tech maintenance/responsibility to the infrastructure team, so if the same set up is possible for the new types, I assume that would be better.

We did work with the composer/installers project to get drupal-recipe a standard composer type. If AI agents, and prompts types are going to be composer require-able projects, we will need to do the same there.

+1 to @thejimbirch's suggestion - and we'd like to follow that same pattern.

If there are thoughts about what the front-end discovery of these projects should look like, that can also be discussed, but that's a bit of a separate issue from what the underlying content type looks like.

It would be great to have some very basic mock-ups of what discovery of AI agents and prompts should look like.

This is exactly what general projects were created for.

When releases of the project have a composer type, like drupal-recipe, we add functionality around that. We could do the same for other non-PHP project metadata if there is a need for it. Projects change their “type” between releases often enough that the “project type” concept breaks down.