skills.rest
backstage
backstageOFFICIAL
Explore all skills by this author →
WebsiteGitHub

app-frontend-system-migration

Migrate Backstage apps from the old frontend system to the extension-based frontend system.

34.1k|7.5k|Updated Jan 24, 2020
Search Tags:#migrate#feature-discovery#backstage#frontend-system#hybrid-migration#extension-based#app-migration
One-click install
npx skills add https://github.com/backstage/backstage --skill app-frontend-system-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-frontend-system-migration
Source: https://github.com/backstage/backstage/tree/main/docs/.well-known/skills/app-frontend-system-migration
Command: npx skills add https://github.com/backstage/backstage --skill app-frontend-system-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to migrating a Backstage app from the old frontend system to the new extension-based frontend system, covering the two-phase hybrid migration and the full migration of routes, sidebar, plugins, APIs, themes, and other app-level concerns.

Core Features & Use Cases

  • Hybrid migration guidance to bridge legacy apps with the new frontend system during Phase 1.
  • Step-by-step conversion of app root, routes, and configuration to enable automatic feature discovery and a seamless upgrade.
  • End-to-end migration best practices for Phase 2, including APIs, themes, icons, translations, and entity pages, to fully adopt the extension-based frontend.

Quick Start

Begin by switching the app's createApp import to @backstage/frontend-defaults and enabling feature discovery to start the hybrid migration.

Frequently Asked Questions about app-frontend-system-migration

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

FAQPage Schema
How do I migrate a Backstage app to the new frontend system?▼

To migrate a Backstage app to the new extension-based frontend system, switch your createApp import to @backstage/frontend-defaults and enable feature discovery to start the Phase 1 hybrid migration process.

What is the difference between Phase 1 hybrid migration and Phase 2 full migration in Backstage?▼

Phase 1 hybrid migration bridges legacy apps with the new frontend system by converting app roots and enabling feature discovery. Phase 2 fully transitions routes, plugins, APIs, themes, and icons to the extension-based architecture.

How do I convert Backstage routes and sidebars to the new frontend system?▼

Converting Backstage routes and sidebars involves transitioning to frontend modules with appropriate tooling and configuration during the migration phases to fully adopt the extension-based frontend architecture.

Can I migrate Backstage themes, APIs, and entity pages to the extension-based frontend?▼

Yes, Phase 2 full migration provides end-to-end best practices for transitioning themes, APIs, icons, translations, and entity pages to fully adopt the extension-based Backstage frontend system.

Does Backstage hybrid migration support automatic feature discovery?▼

Yes, Backstage hybrid migration supports automatic feature discovery by prescribing the conversion of app roots, routes, and configuration to enable a seamless upgrade to the new extension-based frontend system.

Related Skills

Explore More Software Engineering Skills→
olafkfreundolafkfreund

plugin-new-frontend-system-support

Migrate Backstage plugins to support legacy and new frontend systems with dual entry points.

Community
Intermediate
olafkfreundolafkfreund

app-frontend-system-migration

Migrate Backstage apps to the new extension-based frontend system.

Community
Advanced
jacobduijzerjacobduijzer

app-frontend-system-migration

Migrate Backstage apps to the new extension-based frontend system.

Community
Advanced
w020316w020316

feature-evolution

Analyze incremental feature changes and generate change-related tasks from documentation.

Community
Advanced