Front-end plugin wiring for extension-based customization

In Red Hat Developer Hub, front-end wiring uses extension blueprints to govern how dynamic plugins add pages, UI components, icons, and APIs.

Plugins declare their extensions through a default-exported NFS feature at a package entry point by using typed blueprints, such as PageBlueprint, EntityCardBlueprint, and IconBundleBlueprint. A plugin generated by the 2.1 CLI uses the package root; an existing migrated plugin can use ./alpha. The Developer Hub application discovers and loads these extensions by default. Use the app.extensions section of your app-config.yaml file only to disable, reorder, or customize them.