Update header in README

2020-03-20 10:34:40 +01:00
parent 55d22c1f36
commit 8a0b6b1fb8
2 changed files with 4 additions and 3 deletions
@@ -1,21 +1,22 @@
+![headline](headline.png)
+
 # [Backstage](https://backstage.io)

 [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
 ![](https://github.com/spotify/backstage/workflows/Frontend%20CI/badge.svg)
 [![Discord](https://img.shields.io/discord/687207715902193673)](https://discord.gg/EBHEGzX)
+
 ## What is Backstage?

 Backstage is an open platform for building developer portals.

 The philosophy behind Backstage is simple: Don't expose your engineers to the full complexity of your infrastructure tooling. Engineers should be shipping code — not figuring out a whole new toolset every time they want to implement the basics. Backstage allows you add "stuff" (tooling, services, features, etc.) by adding a plugin, instead of building a new tool. This saves you work and avoids the need of your team to learn how to use and support yet another tool.

-![headline](headline.png)
-
 For more information go to [backstage.io](https://backstage.io)

 ## What problem does Backstage solve?

-As companies grow, their infrastructure systems get messier. Backstage unifies all your infrastructure tooling, services, and documentation with a single, consistent UI. 
+As companies grow, their infrastructure systems get messier. Backstage unifies all your infrastructure tooling, services, and documentation with a single, consistent UI.

 This blog post provides more examples of how Backstage is used inside Spotify: