Commerce Project Browser

Find and install Commerce integrations from the screen where you need them. Commerce Project Browser adds Project Browser sources that list Drupal Commerce recipes published on Packagist - including ones not yet on your site - and adds a Browse marketplace button to the admin page where each kind of integration is relevant, such as the payment gateways page.

There is no catalog to maintain. A recipe becomes browsable as soon as its own composer.json says it is a Commerce recipe.

Features

• Context-aware browsing. Each category gets a Browse marketplace button on its own admin page rather than another tab on the Extend page:
  • Payment integrations on the payment gateways page
    (commerce_payment)
  • Shipping integrations on the shipping methods page
    (commerce_shipping)
• Live from Packagist. Lists every drupal-recipe package carrying the matching keyword, with its description, install count and logo.
• Centarro Certified. Recipes Centarro has reviewed carry a Centarro Certified label, can be filtered on, and lead the Most popular ordering.
• One-click install. Uses Project Browser's standard flow: Package Manager runs composer require, then the recipe is applied.
• Extensible. Any module can add a category with a single
  #[ProjectBrowserCategory] plugin class. Its source, browse URL, local action and enabled-source setting are all derived automatically.

Requirements

• Drupal 11
• Project Browser
• Drupal Commerce for the shipped categories. Each category hides itself when the module it relates to is not installed.
• To install recipes from the browser: a working Package Manager setup (an
  up-to-date composer.lock, with any Composer plugins you use listed as trusted).

Installation

composer require drupal/commerce_project_browser
  drush en commerce_project_browser

Nothing to configure. The browse buttons appear on the relevant Commerce admin pages.

For recipe maintainers: get listed

Add the recipe type and keywords to your recipe's composer.json. Tag the specific category and commerce so the recipe also shows up in the catch-all list:

{
      "name": "drupal/commerce_recipe_manual_payment",
      "type": "drupal-recipe",
      "keywords": ["commerce", "commerce_payment"]
  }

Optionally provide a display title and a logo (a full public URL):

"extra": {
      "drupal/commerce_project_browser": {
          "title": "Commerce Recipe: Manual Payment",
          "logo":
  "https://git.drupalcode.org/project/commerce_recipe_manual_payment/-/raw/1.x/logo.png"
      }
  }

Good to know

• Install count is the number of Composer downloads from Packagist, not drupal.org's usage statistics.
• "Maintained" means only that the package is not flagged as abandoned on Packagist.
• Security advisory coverage is not shown. Packagist has no equivalent of drupal.org's policy, so the module does not guess.

Full developer documentation, including how to add a category and the
hook_commerce_project_browser_categories_alter() hook, is in the README.

Related projects

• Project Browser: the browser this module extends
• Drupal Commerce