polybar/doc
patrick96 2c42bae09f refactor(doc): Use cmake APP_VERSION in conf.py
This also moves the doc generation completely into cmake (no more
Makefile).

To generate the docs the project needs to first be configured and then
`make doc` can be run.

The approach used is leaned on the cmake's project own use of Sphinx:
Utilities/Sphinx/CMakeLists.txt
2019-04-05 23:43:37 +02:00
..
bash bash completion 2017-05-19 17:02:47 +02:00
man doc: Add manpage as rst file 2019-04-05 23:43:37 +02:00
zsh feat(ipc): Add visibility commands 2017-05-12 17:55:05 +02:00
CMakeLists.txt refactor(doc): Use cmake APP_VERSION in conf.py 2019-04-05 23:43:37 +02:00
README.md refactor(doc): Use cmake APP_VERSION in conf.py 2019-04-05 23:43:37 +02:00
conf.py.in refactor(doc): Use cmake APP_VERSION in conf.py 2019-04-05 23:43:37 +02:00
config.cmake typo: replace 'alot' with 'a lot' (#1634) 2019-01-29 17:54:38 +01:00
index.rst doc: Add manpage as rst file 2019-04-05 23:43:37 +02:00

README.md

Polybar Manual

The official polybar documentation lives here.

The html documentation and man pages are built automatically when you build with cmake (cmake creates the custom target doc).

Preview Locally

The documentation uses Sphinx with the "Read The Docs" theme sphinx_rtd_theme to generate the documentation, so you will need to have those installed.

To generate the documentation you first need to configure polybar the same as when you compile it (cmake .. in build folder). After that you can run make doc to generate all of the documentation or make doc_html or make doc_man to only generate the html documentation or the man pages.

Open build/doc/html/index.html to read the documentation in the browser.

The manual pages are placed in build/doc/man.