paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 28 Packages Projects Releases Wiki Activity

Update image links to use markdown syntax

Browse Source 
Co-authored-by: Ben Lambert <ben@blam.sh>
Co-authored-by: Fredrik Adelöw <freben@users.noreply.github.com>
Signed-off-by: Johan Haals <johan.haals@gmail.com>
This commit is contained in:
Johan Haals
2023-02-21 11:43:14 +01:00
parent 2b65a84775
commit 7a23cdfa59
10 changed files with 43 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started/index.md
+3 -9
View File
@@ -54,9 +54,7 @@ npx @backstage/create-app@latest
The wizard will ask you for the name of the app, which will also be the name of the directory
<p align='center'>
<img src='../assets/getting-started/wizard.png' alt='Screenshot of the wizard asking for a name for the app.' />
</p>
![Screenshot of the wizard asking for a name for the app.](../assets/getting-started/wizard.png)
### Run the Backstage app
@@ -69,9 +67,7 @@ cd my-backstage-app
yarn dev
```
<p align='center'>
<img src='../assets/getting-started/startup.png' alt='Screenshot of the command output, with the message web pack compiled successfully.'/>
</p>
![Screenshot of the command output, with the message web pack compiled successfully](../assets/getting-started/startup.png)
It might take a little while, but as soon as the message
`[0] webpack compiled successfully` appears, you can open a browser and directly
@@ -80,9 +76,7 @@ You can start exploring the demo immediately. Please note that the in-memory
database will be cleared when you restart the app, so you'll most likely want to
carry on with the database steps.
<p align='center'>
<img src='../assets/getting-started/portal.png' alt='Screenshot of the Backstage portal.'/>
</p>
![Screenshot of the Backstage portal.](../assets/getting-started/portal.png)
In the next part of this tutorial, you'll learn how to change to a persistent
database, configure authentication, and add your first integration. Continue