First off, thank you for considering contributing to this repository! It's people like you that make the open-source community such an amazing place to learn, inspire, and create.
This repository is a personal knowledge base, but I welcome contributions that improve the quality of existing information, add new valuable sections, or enhance the platform's functionality.
If you find a broken link, a technical error in the Docusaurus setup, or a typo in the documentation, please open an issue.
Suggestions for new domains, tool recommendations, or UI improvements are always welcome. Please use the "Feature Request" issue template.
If you want to add a new document or update an existing one:
- Fork the repository.
- Create a new branch:
git checkout -b docs/your-topic-name. - Make your changes in the
docs/directory.- Use proper frontmatter (title, sidebar_position).
- Ensure you use semantic HTML and descriptive headings.
- Submit a Pull Request.
For improvements to the site structure, scripts (like the mindmap generator), or styling:
- Ensure your code follows the existing style patterns.
- Run
yarn buildlocally to ensure no build errors are introduced. - Submit a Pull Request with a clear description of the changes.
- Include a clear, descriptive title for your PR.
- Explain the "why" behind your changes.
- If you're fixing a bug, reference the issue number.
- Ensure all CI checks (deployment preview, linting) pass before requesting a review.
- Tone: Professional, clear, and educational.
- Formatting: Use standard Markdown. For films, follow the nested parent-child list format.
- Images: Place images in
static/img/and reference them using relative paths.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project, you agree to abide by its terms.
Thank you for your contributions!