From 4f9ca91ebf508f2ac9de7f26f6815a68c01cb051 Mon Sep 17 00:00:00 2001 From: Deepthi Ajith Date: Thu, 5 Jun 2025 12:19:06 +0530 Subject: [PATCH] Added caution design changes to building app - converting-3rd party plugin Signed-off-by: Deepthi Ajith --- docs/frontend-system/building-apps/06-plugin-conversion.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/frontend-system/building-apps/06-plugin-conversion.md b/docs/frontend-system/building-apps/06-plugin-conversion.md index 2fab6cf828..88c4b69d45 100644 --- a/docs/frontend-system/building-apps/06-plugin-conversion.md +++ b/docs/frontend-system/building-apps/06-plugin-conversion.md @@ -8,8 +8,9 @@ description: Documentation for how to convert 3rd-party plugins to support the n If you are using or want to use a 3rd-party plugin that does not yet support the new frontend system in your app, you can often use conversion utilities from `@backstage/core-compat-api` in order wrap the plugin to make it possible to install in your app. -> [!CAUTION] -> The purpose of these utilities is to wrap 3rd-party plugins. Do not use them for your own plugins where you can add support for the new frontend system directly. +:::caution +The purpose of these utilities is to wrap 3rd-party plugins. Do not use them for your own plugins where you can add support for the new frontend system directly. +::: ## Converting a legacy plugin