This repository is the main source of developer documentation for Flatpak. It
can be read at docs.flatpak.org <http://docs.flatpak.org/>
_.
Some documentation is also available on the Flatpak wiki and as part of the
flatpak
and flatpak-builder
man pages.
The docs are written in reStructuredText <http://www.sphinx-doc.org/rest.html>
_ and contributions are welcome!
Create a Python virtual environment <https://docs.python.org/3/tutorial/venv.html#creating-virtual-environments>
_::
python3 -m venv .venv && source .venv/bin/activate
Then install the dependencies with pip::
pip install -r requirements.txt sphinx-intl
After setup, you can build the documentation::
make -C docs html
Run the tests::
make -C docs linkcheck
You can run an HTTP server and follow the printed link
(localhost:8000 <http://localhost:8000>
_)
to view the documentation in your browser::
python3 -m http.server -d docs/_build/html
By default, the document being built is in English. If you want to build documents in other languages, such as Chinese, you can use the following command::
sphinx-build -b html -D language=zh_CN docs docs/_build/html/zh_CN
Then you will see the Chinese documentation in the directory
docs/_build/html/zh_CN
.
You can open a pull request adding a new language.
Maintainers can generate the .pot
files by running::
make -C docs gettext
To update .po
files run::
sphinx-intl update -p docs/_build/gettext -d po
Desktop application developers are the primary audience for the Flatpak docs, particularly the authors of existing applications, including those from non-Linux platforms.
The docs should reflect popular practice amongst this audience wherever possible and not assume that applications are coming from the Linux desktop space. In practical terms, this means that we should expect:
.desktop
files, AppStream and D-BusOutside of these basic defaults, special separate attention should be paid to popular cross-platform technologies such as Electron and Qt.
Guidelines for those who want to contribute to the docs: