Thank you for your interest in contributing to the Repo-Booster Documentation! Documentation plays a vital role in helping users understand and use the project effectively. Your contributions are greatly appreciated!
This guide provides instructions for contributing to a Nuxt.js-based documentation site.
- Found a typo, broken link, or confusing section? Open an issue.
- Clearly describe the issue and, if possible, suggest a solution.
- Think a topic is missing or under-documented? Propose it as a new feature request.
- Provide a brief overview of the new section and why it’s valuable.
- Found a way to make the documentation clearer or more user-friendly? Submit your suggestions as a pull request.
-
Ensure the following tools are installed on your system:
-
Fork the repository:
- Click the Fork button in the Repo-Booster Documentation repository.
-
Clone your forked repository:
git clone https://github.com/your-username/documentation.git
-
Navigate into the project directory:
cd documentation
-
Install dependencies:
pnpm install
-
Start the development server:
pnpm dev
The site will be available at
http://localhost:3000
.
-
Create a new branch:
git checkout -b docs/your-change-description
-
Make your edits to the relevant files in the
content
orpages
directory, depending on your site structure. -
Test your changes locally by running the development server:
pnpm dev
-
Commit your changes:
git add . git commit -m "Update [section] for clarity"
-
Push your branch:
git push origin docs/your-change-description
-
Open a pull request:
- Go to the Repo-Booster Documentation repository.
- Navigate to Pull Requests > New Pull Request.
- Select your branch as the source and
main
as the target. - Add a detailed description of your changes.
To maintain consistency across the documentation, please follow these guidelines:
-
Language:
- Use simple and concise language.
- Write in an active voice (e.g., "Click the button" instead of "The button should be clicked").
-
Markdown:
- Use proper Markdown syntax.
- Organize content with headings (
#
,##
,###
). - Use lists (
-
or1.
) where appropriate.
-
Code Blocks:
- Use fenced code blocks for any code or terminal commands:
pnpm install
- Use fenced code blocks for any code or terminal commands:
-
Links:
- Use relative links for internal references (e.g.,
/getting-started
). - Use full URLs for external references.
- Use relative links for internal references (e.g.,
-
Examples and Screenshots:
- Add examples or screenshots whenever possible to make concepts clearer.
This project adheres to the Contributor Covenant Code of Conduct. By participating, you agree to maintain a respectful and inclusive environment. For any issues, contact [[email protected]].
If you encounter any issues or have questions, feel free to:
- Open an issue.
- Email us at [[email protected]].
Thank you for contributing to the Repo-Booster Documentation! Your effort makes a big difference in helping others use this project effectively. 🚀