Our vision for Backstage is for it to become the trusted standard toolbox (read: UX layer) for the open source infrastructure landscape. Think of it like Kubernetes for developer experience. We realize this is an ambitious goal. We can’t do it alone.
Therefore we want to create strong community of contributors -- all working together to create the kind of delightful experience that our developers deserve.
Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given. ❤️
Backstage is released under the Apache2.0 License, and original creations contributed to this repo are accepted under the same license.
No one likes bugs. Report bugs as an issue here.
Look through the GitHub issues for bugs, good first issues or help wanted.
The value of Backstage grows with every new plugin that gets added. Wouldn't it be fantastic if there was a plugin for every infrastructure project out there? We think so. And we would love your help.
A great reference example of a plugin can be found on our blog (thanks @fastfrwrd!)
What kind of plugins should/could be created? Some inspiration from the 120+ plugins that we have developed inside Spotify can be found here, but we will keep a running list of suggestions labeled with [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.
The current documentation is very limited. Help us make the /docs folder come alive.
We think the best way to ensure different plugins provide a consistent experience is through a solid set of reusable UI/UX components. Backstage uses Storybook.
Either help us create new components or improve stories for the existing ones (look for files with *.stories.tsx).
The best way to send feedback is to file an issue.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Use appropriate labels
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
Have you started using Backstage? Adding your company to ADOPTERS really helps the project.
So...feel ready to jump in? Let's do this. 👏🏻💯
Start by reading our Getting Started page. If you need help, just jump into our Discord chatroom.
All code is formatted with prettier using the configuration in the repo. If possible we recommend configuring your editor to format automatically, but you can also use the yarn prettier --write <file> command to format files.
If you're contributing to the backend or CLI tooling, be mindful of cross-platform support. This blog post is a good guide of what to keep in mind when writing cross-platform NodeJS.
Also be sure to skim through our ADRs to see if they cover what you're working on. In particular ADR006: Avoid React.FC and React.SFC is one to look out for.
This project adheres to the Spotify FOSS Code of Conduct. By participating, you are expected to honor this code.
See SECURITY.