Fredrik Adelöw
92feb76252
And also make a proposed split of how the loggers are handled.
Now logs look like
```
{
"type": "incomingRequest",
"service": "backstage",
"timestamp": "2020-04-30T14:29:04.002Z",
"message": "...",
"level": "info"
}
```
for requests, and then if the plugin logs something properly
```
{
"type": "plugin",
"service": "backstage",
"plugin": "inventory",
"timestamp": "2020-04-30T14:29:04.002Z",
"message": "...",
"level": "info"
}
```
Plugins
Backstage is a single-page application composed of a set of plugins.
Our goal for the plugin ecosystem is that the definition of a plugin is flexible enough to allow you to expose pretty much any kind of infrastructure or software development tool as a plugin in Backstage. By following strong design guidelines we ensure the the overall user experience stays consistent between plugins.
Creating a plugin
To create a plugin, follow the steps outlined here.
Suggesting a plugin
If you start developing a plugin that you aim to release as open source, we suggest that you create a new new Issue. This helps the community know what plugins are in development.
You can also use this process if you have an idea for a good plugin but you hope that someone else will pick up the work.