Skip to main content
30 seconds of code is supported by the community. You can contribute in several ways to help improve the project.

​
Ways to help

New content contributions are not accepted at this time.
You can still help by:
  • Reporting bugs or issues with the website
  • Suggesting improvements to existing content
  • Identifying typos or errors in articles
  • Proposing enhancements to the user experience
To report issues or suggest improvements, open an issue on GitHub.

​
Ground rules

Breaking any of these rules will result in your pull request being closed. Follow these guidelines above all else:
Always be polite and respectful to others and try to follow the advice of the maintainer.

​
File modification rules

Only modify files under the content/snippets or content/collections directories when making changes to the website content (bug fixes or improvements). Do not modify:
  • Build configuration files
  • Website source code (unless fixing a bug)
  • Documentation outside the content directories
  • License or attribution files

​
Submitting changes

When submitting a pull request:
  1. Fork the repository and create a new branch for your changes
  2. Make your changes following the writing guidelines
  3. Test your changes locally if possible
  4. Write a clear description of what your PR fixes or improves
  5. Reference any issues that your PR addresses

​
Pull request checklist

Before submitting, verify that:
  • Your changes follow the content guidelines
  • You’ve only modified files in content/snippets or content/collections
  • Your changes are focused on a single issue or improvement
  • You’ve provided a clear explanation of the problem and solution
  • Your tone is respectful and constructive

​
Code of conduct

Be respectful, constructive and helpful in all interactions. The maintainer reserves the right to close any issue or pull request that violates these principles. Remember that the maintainer is volunteering their time to review your contribution. Make their job easier by following these guidelines carefully.

Build docs developers (and LLMs) love

Get started for freeTalk to us