No description
  • HTML 51.9%
  • Shell 48.1%
Find a file
Haelwenn 42c38959f6 Merge branch 'alpine-all-stable' into 'master'
CI: Switch all to alpine:latest, all deps are in stable

See merge request pleroma/docs!11
2025-01-17 06:29:15 +00:00
docs docs/index: Change reference of freenode to libera.chat 2021-05-31 16:58:31 +02:00
theme/partials Make source partitial have different links depending on which project 2019-10-03 18:28:15 +03:00
.gitignore CI: Use Alpine packages instead of pip 2023-01-23 08:33:55 +01:00
.gitlab-ci.yml CI: Switch all to alpine:latest, all deps are in stable 2025-01-17 07:26:31 +01:00
manage.sh Fix branch detection and hardcode fe branch to be develop 2019-10-03 14:57:34 +03:00
mkdocs.yml Lock dependencies with pipenv 2020-08-14 15:02:03 +03:00
Pipfile Lock dependencies with pipenv 2020-08-14 15:02:03 +03:00
README.md CI: Use Alpine packages instead of pip 2023-01-23 08:33:55 +01:00
renovate.json Add renovate.json 2022-12-10 09:10:15 +00:00

Pleroma documentation

This project contains a documentation skeleton and a script to fill it in with data, the resulting documentation can be viewed at https://docs-develop.pleroma.social.

Contributing to the documentation

If you want to suggest an edit, please refer to the pleroma/pleroma and pleroma/pleroma-fe repos.

We use mkdocs to build the documentation and have the admonition extensions that make it possible to add block-styled side content like example summaries, notes, hints or warnings. If you are unsure of how a specific syntax should look like, feel free to look through the docs for an example.

Building the docs

You don't need to build and test the docs as long as you make sure the syntax is correct. But in case you do want to build the docs, feel free to do so.

1. Dependencies

Getting dependencies on an Alpine edge system

sudo apk add git mkdocs-material py3-markdown-include py3-regex

Getting dependencies on a generic distro via pipenv

pip install pipenv
pipenv install

Since dependencies are installed in a virtual environment, you can't use them directly. To use them you should either prefix the command with pipenv run, or activate the virtual environment for current shell by executing pipenv shell once.

2. Build the docs using the script

To build the docs you can clone this project and use the manage.sh script, like so:

git clone https://git.pleroma.social/pleroma/docs
cd docs
[pipenv run] ./manage.sh all

./manage.sh all will fetch the docs from the pleroma and pleroma-fe repos and build the documentation locally. To see what other options you have, do ./manage.sh --help.

3. Serve the files

A folder site containing the static html pages will have been created. You can serve them from a server by pointing your server software (nginx, apache...) to this location. During development, you can run locally with

[pipenv run] mkdocs serve

This handles setting up an http server and rebuilding when files change. You can then access the docs on http://127.0.0.1:8000