Merge pull request #27672 from Parsifal-M/docs/getting-started-21828

[DOCS] Restructure the Getting Started Section

docs/getting-started/concepts.md

@@ -1,21 +0,0 @@
----
-id: concepts
-title: Key Concepts
-# prettier-ignore
-description: High level key concepts used in the Backstage project
----
-
-For users of Backstage, there are certain concepts which are central to its
-design and functionality. Being an expert in each of these concepts is not
-necessary, however having a base understanding of each will make administering,
-configuring, and operating Backstage easier.
-
-- CHANGELOG - https://keepachangelog.com
-- Docker - https://www.docker.com/
-- Monorepo - https://semaphoreci.com/blog/what-is-monorepo
-- Node.js - https://nodejs.org
-- React - https://reactjs.org
-- Semantic Versioning - https://semver.org
-- TypeScript - https://www.typescriptlang.org
-- YAML - https://yaml.org
-- Yarn - https://www.pluralsight.com/guides/yarn-a-package-manager-for-node-js

docs/getting-started/configure-app-with-plugins.md

@@ -4,6 +4,14 @@ title: Configuring App with plugins
 description: Documentation on How Configuring App with plugins
 ---
 
+Audience: Developers
+
+:::note Note
+Backstage plugins are primarily written using [TypeScript](https://www.typescriptlang.org), [Node.js](https://nodejs.org) and [React](https://reactjs.org). Having an understanding of these technologies will be beneficial on your journey to customizing Backstage!
+:::
+
+## Summary
+
 Backstage plugins customize the app for your needs. There is a
 [plugin directory](https://backstage.io/plugins) with plugins for many common
 infrastructure needs - CI/CD, monitoring, auditing, and more.

docs/getting-started/index.md

@@ -7,6 +7,10 @@ description: How to install Backstage for your own use.
 
 Audience: Developers and Admins
 
+:::note Note
+It is not required, although recommended to have a basic understanding of [Yarn](https://www.pluralsight.com/guides/yarn-a-package-manager-for-node-js) and [npm](https://docs.npmjs.com/about-npm) before starting this guide.
+:::
+
 ## Summary
 
 This guide walks through how to get started creating your very own Backstage customizable app. This is the first step in evaluating, developing on, or demoing Backstage.
@@ -21,7 +25,7 @@ If you are planning to contribute a new feature or bug fix to the Backstage proj
 
 ## Prerequisites
 
-This guide assumes a basic understanding of working on a Linux based operating system and have some experience with the terminal, specifically, these commands: `npm`, `yarn`.
+This guide also assumes a basic understanding of working on a Linux based operating system and have some experience with the terminal, specifically, these commands: `npm`, `yarn`.
 
 - Access to a Unix-based operating system, such as Linux, macOS or
   [Windows Subsystem for Linux](https://docs.microsoft.com/en-us/windows/wsl/)

docs/getting-started/keeping-backstage-updated.md

@@ -4,6 +4,14 @@ title: Keeping Backstage Updated
 description: How to keep your Backstage App updated
 ---
 
+Audience: Developers and Admins
+
+:::note Note
+To better understand the concepts in this section, it's recommended to have an understanding of [Monorepos](https://semaphoreci.com/blog/what-is-monorepo), [Semantic Versioning](https://semver.org) and [CHANGELOGs](https://keepachangelog.com).
+:::
+
+## Summary
+
 Backstage is always improving, so it's a good idea to stay in sync with the
 latest releases. Backstage is more of a library than an application or service;
 similar to `create-react-app`, the `@backstage/create-app` tool gives you a

docs/getting-started/register-a-component.md

@@ -6,6 +6,10 @@ description: Start populating your Backstage app with your data.
 
 Audience: Developers
 
+:::note Note
+Entity files are stored in YAML format, if you are not familiar with YAML, you can learn more about it [here](https://yaml.org).
+:::
+
 ## Summary
 
 This guide will walk you through how to pull Backstage data from other locations manually. There are integrations that will automatically do this for you.