Reference checklist of things to avoid gatekeeping in posts, articles, videos, talks, presentations, podcasts, and in any other content.
It is your job to make sure that every piece of content you put out is inclusive, accessible, and welcoming to all. This checklist is here to make your life easier. No longer will you need to remeber every single thing you need to do in order to stop accidental gatekeeping in your content.
- Fork the repository.
- Add a new row to adopters section on homepage, with your community, project's name, or company linked to your site in the first column. Then, after the arrow add what you're using OpenGates for in the second column. Example below
- Open a pull request.
- [Vicki Langer](https://twitter.com/Vicki_Langer) → Writing dev.to content & a beginners python book
- [You]() → something awesome?
If you would like to contribute, feel free to make a pull request.
First time? I suggest checking out issue #1 to add items for more details.
If you need more of a step-by-step, skim through this article about making your first contribution.
This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
All contributions are greatly appreciated.