Thank you for considering contributing to CampX! We welcome contributions from the community to help improve and expand the project. Whether you're fixing bugs, adding new features, improving documentation, or sharing ideas, your contributions are highly appreciated.
Please follow our Code of Conduct to ensure a welcoming and inclusive environment for everyone.
If you're new to Git and GitHub, no worries! Here are some useful resources:
- Forking a Repository
- Cloning a Repository
- How to Create a Pull Request
- Getting Started with Git and GitHub
- Learn GitHub from Scratch
CAMPX/
├── .github/ # GitHub-related configurations workflows, issue templates
├── cloudinary/ # Cloudinary configuration and integration
├── controllers/ # Handles incoming requests and business logic
│ ├── campgrounds.js # Controls campground-related actions e.g., creating, editing, deleting
│ ├── reviews.js # Manages review submissions and interactions
│ ├── users.js # Handles user authentication, authorization, and profile management
├── models/ # Defines data structures for database interactions
│ ├── campground.js # Represents campground data (name, description, location, etc.)
│ ├── review.js # Represents review data (rating, comment, user reference)
│ ├── user.js # Represents user data (username, email, password, role)
├── public/ # Static assets
│ ├── icons/ # Custom icons and font icons
│ ├── javascripts/
│ ├── stylesheets/
├── routes/ # Defines API endpoints and routes
│ ├── campgrounds.js
│ ├── reviews.js
│ ├── users.js
├── seeds/ # Scripts for populating the database with initial data
│ ├── cities.js
│ ├── index.js
│ ├── seedHelpers.js
├── utils/ # General utility functions
│ ├── ExpressError.js # Custom error handling class
│ ├── catchAsync.js # Error handling middleware
│ ├── constant.js # Defines global constants and configuration
├── views/ # Templates for rendering dynamic HTML
│ ├── campgrounds/
│ ├── layouts/
│ ├── partials/
│ ├── users/
│ ├── error.ejs
│ ├── home.ejs
├── .gitignore # Files and directories to ignore in Git
├── .gitpod.yml
├── app.js # Main application file, initializes the server
├── CHANGELOG.md
├── CODE_OF_CONDUCT.md # Code of conduct guidelines
├── CONTRIBUTING.md # Guidelines for contributing to the project
├── cron.js # Scheduled tasks (e.g., sending emails, cleaning up data)
├── INSTALLATION.md
├── LICENSE
├── middleware.js
├── package-lock.json
├── package.json # Project dependencies and configuration
├── README.md # Project overview and documentation
├── schemas.md
├── SECURITY.md # Security considerations and best practices
-
Star this repository Click on the top right corner marked as Stars at last.
-
Fork this repository Click on the top right corner marked as Fork at second last.
-
Clone the forked repository
git clone https://github.com/<your-github-username>/CampX.git- Navigate to the project directory
cd CampX- Create a new branch
git checkout -b <your_branch_name>- To make changes
git add .- Now to commit
git commit -m "add comment according to your changes or addition of features inside this"- Push your local commits to the remote repository
git push -u origin <your_branch_name>-
Create a Pull Request
-
Congratulations! 🎉 you've made your contribution
-
Open GitHub Desktop: Launch GitHub Desktop and log in to your GitHub account if you haven't already.
-
Clone the Repository:
- If you haven't cloned the Project-Guidance repository yet, you can do so by clicking on the "File" menu and selecting "Clone Repository."
- Choose the Project-Guidance repository from the list of repositories on GitHub and clone it to your local machine.
3.Switch to the Correct Branch:
- Ensure you are on the branch that you want to submit a pull request for.
- If you need to switch branches, you can do so by clicking on the "Current Branch" dropdown menu and selecting the desired branch.
- Make Changes:
- Make your changes to the code or files in the repository using your preferred code editor.
- Commit Changes:
- In GitHub Desktop, you'll see a list of the files you've changed. Check the box next to each file you want to include in the commit.
- Enter a summary and description for your changes in the "Summary" and "Description" fields, respectively. Click the "Commit to " button to commit your changes to the local branch.
- Push Changes to GitHub:
- After committing your changes, click the "Push origin" button in the top right corner of GitHub Desktop to push your changes to your forked repository on GitHub.
- Create a Pull Request:
- Go to the GitHub website and navigate to your fork of the Project-Guidance repository.
- You should see a button to "Compare & pull request" between your fork and the original repository. Click on it.
- Review and Submit:
- On the pull request page, review your changes and add any additional information, such as a title and description, that you want to include with your pull request.
- Once you're satisfied, click the "Create pull request" button to submit your pull request.
- Wait for Review: Your pull request will now be available for review by the project maintainers. They may provide feedback or ask for changes before merging your pull request into the main branch of the Project-Guidance repository.
-
Follow the Project's Code Style
- Maintain consistency with the existing code style (indentation, spacing, comments).
- Use meaningful and descriptive names for variables, functions, and classes.
- Keep functions short and focused on a single task.
- Avoid hardcoding values; instead, use constants or configuration files when possible.
-
Write Clear and Concise Comments
- Use comments to explain why you did something, not just what you did.
- Avoid unnecessary comments that state the obvious.
- Document complex logic and functions with brief explanations to help others understand your thought -process.
-
Keep Code DRY (Don't Repeat Yourself)
- Avoid duplicating code. Reuse functions, methods, and components whenever possible.
- If you find yourself copying and pasting code, consider creating a new function or component.
-
Write Tests
- Write unit tests for your functions and components.
- Ensure your tests cover both expected outcomes and edge cases.
- Run tests locally before making a pull request to make sure your changes don’t introduce new bugs.
-
Code Reviews and Feedback
- Be open to receiving constructive feedback from other contributors.
- Conduct code reviews for others and provide meaningful suggestions to improve the code.
- Always refactor your code based on feedback to meet the project's standards.
When submitting a pull request, please adhere to the following:
- Self-review your code before submission. 😀
- Include a detailed description of the functionality you’ve added or modified.
- Comment your code, especially in complex sections, to aid understanding.
- Add relevant screenshots to assist in the review process.
- Submit your PR using the provided template and hang tight; we'll review it as soon as possible! 🚀
To report an issue, follow these steps:
- Navigate to the project's issues section :- Issues
- While raising an issue kindly choose the appropriate template for your issue.
- Provide a clear and concise description of the issue.
- Wait until someone looks into your report.
- Begin working on the issue only after you have been assigned to it. 🚀
We truly appreciate your time and effort to help improve our project. Feel free to reach out if you have any questions or need guidance. Happy coding! 🚀