2.6 KiB
Help
We want to make sitespeed.io the best web performance tool in the world and we hope you can to help us!
Developers
We love to have more people involved in making sitespeed.io better. We are constantly working on adding more documentation and trying to write more information in the issues so its easier to help out. If there's an issue that you want to take on, ping the the issue and we can help you get started. You can also join our Slack channel if you need help!
Designers
As a designer there's a lot you can do: You can make the HTML result pages look better. Maybe we should restructure the metrics? Maybe we should have graphs? Or could the header/footer look better? You could also have look at https://www.sitespeed.io where we have all the documentation. Make it look phab. You can pretty much help us with everything, no one in the core team got design skills :)
Documentation
Documentation is fun and it is the core of making sitespeed.io easy to use. We got a special documentation tag for issues that you can use to find where we know we lack documentation. Fixing spelling mistakes is great. Or rewrite parts that you think is too complicated. You can find what you need to send a PR to the documentation here.
Tests
We lack unit tests. You can read about our testing pipeline that works good for us but more unit tests are always good. A good start is adding support for the code in the support library.
Companies
Do you use sitespeed.io in your everyday work? Then we have a perfect proposition for you! Have a hack day with focus on sitespeed.io for your team and contribute back. Pick one the things in the Help wanted section. Or maybe there's a function you think is missing? Create it. Contribute back.
Help wanted
You can help us:
- Make it possible to drive Chrome on Android phones from Docker.
- Add connectivity support for Android phones.
- Help us make the documentation even better. We love your feedback and help https://github.com/sitespeedio/sitespeed.io/tree/master/docs.