plugin-new-frontend-system-support

Add dual frontend system support to Backstage plugins with alpha entries and PageBlueprints.

Updated Mar 27, 2026

Search Tags:#frontend #migration #plugin #alpha #backstage #dual-entry #pageblueprint

Ready to run

npx skills add https://github.com/transaurus/staging-backstage-backstage --skill plugin-new-frontend-system-support-transaurus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-new-frontend-system-support
Source: https://github.com/transaurus/staging-backstage-backstage/tree/main/docs/.well-known/skills/plugin-new-frontend-system-support
Command: npx skills add https://github.com/transaurus/staging-backstage-backstage --skill plugin-new-frontend-system-support-transaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add new frontend system support to an existing Backstage plugin while keeping the old system working. Use this skill for published or shared plugins that need to work in both old and new frontend system apps.

Core Features & Use Cases

Dual entry point: maintain existing src/plugin.ts (old system) while adding a new src/alpha.tsx (new system) to support both frontends.
PageBlueprint integration: leverage PageBlueprint to render the new system pages without imposing the old shell.
Published/shared plugin readiness: ideal for plugins used by external parties that must work in environments using either frontend system.

Quick Start

Create an alpha entry point, wire a PageBlueprint to load your NFS page, and export the Nfs variant so users can opt into the new frontend system.

Frequently Asked Questions about plugin-new-frontend-system-support

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add new frontend system support to a Backstage plugin without breaking the old system?▼

To add new frontend system support while keeping the old system working, you create a dual entry point by maintaining src/plugin.ts for the old system and adding a new src/alpha.tsx entry for the new system.

What is the dual-entry pattern for Backstage plugin migration?▼

The dual-entry pattern preserves your existing src/plugin.ts entry point while introducing an alpha entry point (src/alpha.tsx) to support the new frontend system, ensuring backward compatibility.

Does my published Backstage plugin need dual frontend support to work in new apps?▼

Published or shared Backstage plugins need dual frontend support to operate in both old and new app architectures, allowing external parties to use your plugin regardless of their frontend system.

How do I use PageBlueprint to render Backstage plugin pages in the new frontend system?▼

You use PageBlueprint in your alpha entry point to render new system pages without imposing the old shell, and optionally leverage SubPageBlueprints for structured navigation within the new frontend system.

When should I avoid adding an alpha entry point to my Backstage plugin?▼

If your Backstage plugin is private and only used within a single old frontend system app, adding an alpha entry point for dual frontend support may be unnecessary overhead.