This guide will help you get started with contributing to the documentation for Zen Browser. The documentation is crucial for helping users and developers understand and use the project effectively. We use Fumadocs for generating the static documentation site.
Before you begin, ensure you have the following tools installed:
- Git: Version control system to clone the repository and manage your code.
- Node.js: Required for building the Quartz v4 site.
- npm: Node package manager, which comes with Node.js.
- IDE of your choice: You can use any text editor or IDE of your choice.
- Navigate to the Zen Browser Documentation Repository.
- Click on the "Fork" button at the top right of the repository page to create a personal copy of the repository under your GitHub account.
Once you have forked the repository, clone it to your local machine using the following command:
git clone https://github.com/<your-username>/docs.git
cd docs
Replace <your-username>
with your GitHub username.
Navigate to the project directory and install the required dependencies:
npm install
This command installs all the necessary packages listed in the package.json
file.
Open the cloned repository folder in your IDE to begin editing:
- Open IDE.
- Select "Open Folder" or "File > Open Folder".
- Navigate to the cloned repository folder.
You can now start editing the documentation. The project structure is as follows:
content/docs/
- contains the Markdown files for the documentation.public/assets/
- contains images and other static assets used in the documentation.src/
- contains the source code for the documentation site. No changes are required here.
- Follow the existing structure and formatting conventions.
- Use clear and concise language.
- Include examples and code snippets where applicable.
- Ensure all links and references are accurate.
To preview the documentation site locally, run the following command:
npm run dev
# or
pnpm dev
# or
yarn dev
This command starts a local server running on http://localhost:3000
that you can access from your browser. The site will automatically reload whenever you make changes to the Markdown files.
Once you are satisfied with your changes, commit them to your local repository:
git add .
git commit -m "Description of your changes"
Push your changes to your forked repository:
git push origin main
After pushing your changes, go to the original Zen Browser Documentation Repository and submit a pull request:
- Navigate to the repository you forked from.
- Click on the "Pull Requests" tab.
- Click on "New Pull Request" and select your branch.
- Provide a clear and concise description of your changes.
- Submit the pull request.
Your pull request will be reviewed by the maintainers, and you may be asked to make some adjustments. Once approved, your changes will be merged into the main branch.
- Zen Browser Documentation Repository
- Fumadocs Documentation
- Contribution Guidelines
- Code of Conduct
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
Thank you for contributing to Zen Browser's documentation! Your contributions help users and developers understand and effectively use the project.