Contrib.social

Support "non-traditional" project types

Open on Drupal.org →
Created on 19 August 2025, 4 days ago

Problem/Motivation

Drupal CMS and AI module (probably the list is not full) have introduced new types of shareable items that hardly fit existing project types on https://www.drupal.org/project/add: → recipes, AI agents, and prompts.

While different in nature, they are by design much simpler and smaller, often do not have any changes history or have very limited one, are interchangeable and often do not require any development skills to create.

Given the ease of creation, I could imagine there are (by the orders of magnitude) more recipes or agents than there are modules or themes.

There could be also significant overlapping for recipes or prompts that serve the same purpose, so probably there should also be a concept of collections.

It would be good to have these new project types (if that's still would be projects) on drupal.org

Remaining tasks

  1. Decide what type of entity are those new projects: are those projects in the same understanding as module or community page? Or something different
  2. Can these new projects be hosted on drupal.org? What are the requirements/limitations
✨ Feature request
Status

Active

Version

1.0

Component

Marketplace

Created by

🇧🇬Bulgaria valthebald Sofia

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @valthebald
  • Comment 4 days ago →
    🇺🇸United States Kristen Pol Santa Cruz, CA, USA

    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.

  • Comment 4 days ago →
    🇺🇸United States thejimbirch Cape Cod, Massachusetts

    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.

  • Comment 4 days ago →
    🇺🇸United States hestenet Portland, OR 🇺🇸

    +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.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024