-
Notifications
You must be signed in to change notification settings - Fork 73
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #134 from niccokunzmann/docs-docs
Add documentation.md file
- Loading branch information
Showing
2 changed files
with
65 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,64 @@ | ||
# Documentation | ||
|
||
The Pixelfed documentation can be found at [docs.pixelfed.org]. | ||
The source code repository for the documentation is hosted on GitHub at [pixelfed/docs]. | ||
If you find any mistakes in the documentation, please have a look at the [open issues](https://github.com/pixelfed/pixelfed-docs) and open a new one if yours does not exist. | ||
|
||
## Contributing to Documentation | ||
|
||
The following sections should get you started on contributing to the documentation of Pixelfed. | ||
Before getting started, please read the [Code of Conduct]. | ||
|
||
## Writing Documentation Online | ||
|
||
To get started writing the documentation, you only need a GitHub account. | ||
You can find the documentation in its [GitHub repository][pixelfed/docs]. | ||
Find the right page and after log-in, you can see an edit button above the document. | ||
Please create a Pull Request with your changes. | ||
We are using [Markdown] as the format for the documentation files (`.md`). | ||
|
||
[Markdown]: https://www.markdownguide.org/cheat-sheet/ | ||
|
||
## Building the Documentation Locally | ||
|
||
For most additions and changes to the documentation, you do not need to build the documentation locally. | ||
|
||
If you choose to build the documentation website on your own computer, follow these steps: | ||
|
||
1. Clone the [pixelfed/docs] repository. | ||
|
||
```sh | ||
git clone https://github.com/pixelfed/docs.git pixelfed-docs | ||
cd pixelfed-docs | ||
``` | ||
|
||
2. Install [node and npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm). | ||
3. Install [VitePress] and the other dependencies. | ||
|
||
```sh | ||
# in the pixelfed-docs directory | ||
npm install | ||
``` | ||
|
||
4. Build and serve the documentation: | ||
|
||
```sh | ||
npm run docs:dev | ||
``` | ||
|
||
Then, visit [localhost:5173](http://localhost:5173/) in your browser. | ||
It should look like [docs.pixelfed.org]. | ||
Now, whenever you change a file, it should automatically reload with the changes. | ||
|
||
## Related Links | ||
|
||
- [Markdown] | ||
- [VitePress] | ||
- [Code of Conduct] | ||
- [The official documentation][docs.pixelfed.org] | ||
- [The documenation repository][pixelfed/docs] | ||
|
||
[VitePress]: https://vitepress.dev/ | ||
[docs.pixelfed.org]: https://docs.pixelfed.org | ||
[Code of Conduct]: https://github.com/pixelfed/docs/blob/main/CODE_OF_CONDUCT.md | ||
[pixelfed/docs]: https://github.com/pixelfed/docs |