Thank you for considering contributing to Zapher! We appreciate your support and are excited to work with you. This document outlines the steps and guidelines for contributing to the project.
There are several ways you can contribute to Zapher:
- Reporting bugs
- Suggesting features
- Improving documentation
- Writing code for new features or bug fixes
If you encounter any bugs, please report them by following these steps:
- Search for existing issues to ensure the bug hasn't been reported already.
- Open a new issue if you can't find an existing one.
- Include detailed information about the bug:
- Steps to reproduce
- Expected behavior
- Actual behavior
- Screenshots or logs, if applicable
We welcome new feature suggestions! To suggest a feature:
- Search for existing feature requests to avoid duplicates.
- Open a new issue if you can't find an existing one.
- Provide a detailed description of the feature:
- The problem it solves
- How it would benefit users
- Any implementation ideas you have
Good documentation is crucial for any project. You can help by:
- Fixing typos or grammatical errors
- Clarifying existing documentation
- Writing new documentation for features or processes
-
Fork the repository by clicking the "Fork" button at the top right of the GitHub page.
-
Clone your forked repository to your local machine:
git clone https://github.com/yourusername/zapher.git cd zapher
-
Add the upstream repository:
git remote add upstream https://github.com/originalowner/zapher.git
-
Create a new branch for your feature or bug fix:
git checkout -b feature-branch
-
Make your changes in the new branch.
-
Commit your changes with a meaningful commit message:
git add . git commit -m "Description of your changes"
-
Push your changes to your forked repository:
git push origin feature-branch
- Go to your forked repository on GitHub.
- Click on the "Compare & pull request" button next to your branch.
- Provide a descriptive title and detailed description of your changes.
- Submit the pull request.
- Follow the coding style used in the existing codebase.
- Write clear, concise, and meaningful commit messages.
- Ensure your code passes all tests and lint checks.
- Write tests for new features or bug fixes.
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.
Join our community to ask questions, share ideas, and get support:
If you're new to the technologies used in Zapher, here are some resources to get you started:
- JavaScript: JavaScript Tutorial
- Next.js: Next.js Tutorial
- Clerk: Clerk Tutorial
- Git and GitHub: GitHub Docs
Thank you for taking the time to contribute to Zapher. Your help is appreciated, and we look forward to working with you!
If you have any questions or need further assistance, feel free to open an issue or contact us via the community channels.
Happy coding!