Where to get support
- Start by reading the Bridgetown Documentation.
- Kick off a discussion on the Bridgetown Community Forum.
- Chat with Bridgetowners live on our Discord server.
There are a bunch of helpful core team and community members available that should be able to point you in the right direction.
There are also a growing number of companies which provide commercial support for advanced Bridgetown site builds. These include:
Ways to contribute
Whether you’re a developer, designer, or overall Bridgetown enthusiast, there are lots of ways to contribute. Here’s a few ideas:
- Comment on some of the project’s open issues. Have you experienced the same problem? Know a work around? Do you have a suggestion for how the feature could be better?
- Read through the documentation and file a pull request (PR) by forking the Bridgetown repo on GitHub and adding your changes or suggestions for something that could be improved.
- Browse through the Bridgetown community forum and lend a hand answering questions or proposing awesome new features. There’s a good chance other folks are in the same boat as you.
- Help evaluate open pull requests by testing the changes locally and reviewing what’s proposed. Or if you have a PR you’d like to submit for a new feature or a bugfix, we’d be thrilled to evaluate it and guide it through the release cycle if it adheres to our roadmap and project goals.
Reminder: Bridgetown’s issue tracker on GitHub is not a support forum. Only file issues for reproducible problems you’ve identified while using Bridgetown.
Bridgetown Contributor Code of Conduct
As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
Read our full code of conduct.
Want to give us a public shoutout? Check out our official Twitter account!