From 838dd945da97e977397fb4b827f6f7db5234281d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fredrik=20Adel=C3=B6w?= Date: Sat, 15 Jan 2022 22:53:54 +0100 Subject: [PATCH] prettier MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Fredrik Adelöw --- docs/overview/architecture-overview.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/overview/architecture-overview.md b/docs/overview/architecture-overview.md index d08d9cbdcd..5d27cc4184 100644 --- a/docs/overview/architecture-overview.md +++ b/docs/overview/architecture-overview.md @@ -202,14 +202,14 @@ with a smaller collection of plugins. ### Plugin Packages A typical plugin consists of up to five packages, two frontend ones, two -backend, and one isomorphic package. All packages within the plugin must share -a common prefix, typically of the form `@/plugin-`, but +backend, and one isomorphic package. All packages within the plugin must share a +common prefix, typically of the form `@/plugin-`, but alternatives like `backstage-plugin-` or `@scope/backstage-plugin-` are also valid. Along with this prefix, each of the packages have their own unique suffix that denotes their role. In -addition to these five plugin packages it's also possible for a plugin to -have additional frontend and backend modules that can be installed to enable -optional features. For a full list of suffixes and their roles, see the +addition to these five plugin packages it's also possible for a plugin to have +additional frontend and backend modules that can be installed to enable optional +features. For a full list of suffixes and their roles, see the [Plugin Package Structure ADR](../architecture-decisions/adr011-plugin-package-structure.md). The `-react`, `-common`, and `-node` plugin packages together form the external @@ -246,10 +246,10 @@ however likely to change in the future. ### Common Packages -The common packages are the packages effectively depended on by all other -pages. This is a much smaller set of packages but they are also very pervasive. -Because the common packages are isomorphic and must execute both in the frontend -and backend, they are never allowed to depend on any of the frontend of backend +The common packages are the packages effectively depended on by all other pages. +This is a much smaller set of packages but they are also very pervasive. Because +the common packages are isomorphic and must execute both in the frontend and +backend, they are never allowed to depend on any of the frontend of backend packages. The Backstage CLI is in a category of its own and is depended on by virtually