docs: sunset the docs/plugins section as legacy documentation
Mark all pages in docs/plugins/ with legacy admonition banners pointing to the appropriate new frontend system and backend system documentation. Rename the sidebar section to "Plugins (Legacy)" and move it lower in the navigation hierarchy. Add cross-references from the new frontend system building-plugins guide to relevant cross-cutting topics (i18n, analytics, feature flags, search) that still live in the legacy section. Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com> Made-with: Cursor
This commit is contained in:
@@ -4,6 +4,12 @@ title: Feature Flags
|
||||
description: Details the process of defining setting and reading a feature flag.
|
||||
---
|
||||
|
||||
:::caution Legacy Documentation
|
||||
|
||||
This page describes feature flags using the **old frontend system** APIs (`createPlugin` from `@backstage/core-plugin-api` and `createApp` from `@backstage/app-defaults`). For the new frontend system, feature flags are declared via the `featureFlags` option in `createFrontendPlugin` — see [Building Frontend Plugins](../frontend-system/building-plugins/01-index.md). The `FeatureFlagged` component and `featureFlagsApiRef` work the same way in both systems.
|
||||
|
||||
:::
|
||||
|
||||
Backstage offers the ability to define feature flags inside a plugin or during application creation. This allows you to restrict parts of your plugin to those individual users who have toggled the feature flag to on.
|
||||
|
||||
This page describes the process of defining, setting and reading a feature flag. If you are looking for using feature flags specifically with software templates please see [Writing Templates](https://backstage.io/docs/features/software-templates/writing-templates#remove-sections-or-fields-based-on-feature-flags).
|
||||
|
||||
Reference in New Issue
Block a user