Skip to content

Commit d6b3110

Browse files
authored
Merge pull request #134 from niccokunzmann/docs-docs
Add documentation.md file
2 parents d1789f3 + f4b83ca commit d6b3110

File tree

2 files changed

+65
-0
lines changed

2 files changed

+65
-0
lines changed

.vitepress/config.mjs

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,7 @@ export default defineConfig({
3232
items: [
3333
{ text: 'Introduction', link: '/project/introduction' },
3434
{ text: 'Community', link: '/project/community' },
35+
{ text: 'Documentation', link: '/project/documentation' },
3536
]
3637
},
3738
{

project/documentation.md

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
# Documentation
2+
3+
The Pixelfed documentation can be found at [docs.pixelfed.org].
4+
The source code repository for the documentation is hosted on GitHub at [pixelfed/docs].
5+
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.
6+
7+
## Contributing to Documentation
8+
9+
The following sections should get you started on contributing to the documentation of Pixelfed.
10+
Before getting started, please read the [Code of Conduct].
11+
12+
## Writing Documentation Online
13+
14+
To get started writing the documentation, you only need a GitHub account.
15+
You can find the documentation in its [GitHub repository][pixelfed/docs].
16+
Find the right page and after log-in, you can see an edit button above the document.
17+
Please create a Pull Request with your changes.
18+
We are using [Markdown] as the format for the documentation files (`.md`).
19+
20+
[Markdown]: https://www.markdownguide.org/cheat-sheet/
21+
22+
## Building the Documentation Locally
23+
24+
For most additions and changes to the documentation, you do not need to build the documentation locally.
25+
26+
If you choose to build the documentation website on your own computer, follow these steps:
27+
28+
1. Clone the [pixelfed/docs] repository.
29+
30+
```sh
31+
git clone https://github.com/pixelfed/docs.git pixelfed-docs
32+
cd pixelfed-docs
33+
```
34+
35+
2. Install [node and npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm).
36+
3. Install [VitePress] and the other dependencies.
37+
38+
```sh
39+
# in the pixelfed-docs directory
40+
npm install
41+
```
42+
43+
4. Build and serve the documentation:
44+
45+
```sh
46+
npm run docs:dev
47+
```
48+
49+
Then, visit [localhost:5173](http://localhost:5173/) in your browser.
50+
It should look like [docs.pixelfed.org].
51+
Now, whenever you change a file, it should automatically reload with the changes.
52+
53+
## Related Links
54+
55+
- [Markdown]
56+
- [VitePress]
57+
- [Code of Conduct]
58+
- [The official documentation][docs.pixelfed.org]
59+
- [The documenation repository][pixelfed/docs]
60+
61+
[VitePress]: https://vitepress.dev/
62+
[docs.pixelfed.org]: https://docs.pixelfed.org
63+
[Code of Conduct]: https://github.com/pixelfed/docs/blob/main/CODE_OF_CONDUCT.md
64+
[pixelfed/docs]: https://github.com/pixelfed/docs

0 commit comments

Comments
 (0)