polybar/doc
patrick96 c34f013e5f doc: Reflect config fallback in config
This should reflect the changes from #2026
2020-11-23 13:16:37 +01:00
..
dev doc: Write new release workflow 2020-11-22 23:32:41 +01:00
man doc: Reflect config fallback in config 2020-11-23 13:16:37 +01:00
.gitignore build: Allow doc to build as its own project 2019-05-10 08:14:02 +02:00
CMakeLists.txt doc: Set SPHINX_BUILD in standalone doc builds 2020-10-03 15:37:17 +02:00
README.md doc: Update links to https (#2012) 2020-02-21 15:39:39 +01:00
conf.py doc: Add '(unreleased)' tag for unreleased versions (#2118) 2020-06-07 21:54:04 +02:00
index.rst doc: Write new release workflow 2020-11-22 23:32:41 +01: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 to generate the documentation, so you will need to have that installed.

If you build polybar normally while having Sphinx installed during configuration, the documentation will be enabled and built as well. Building the documentation can be disabled by passing -DBUILD_DOC=OFF to cmake.

Alternatively the documentation can be built without the rest of polybar, for that run cmake only on the doc directory. For example, create a build directory in doc and then run cmake .. in there.

Once configured, all of the documentation can be generated with make doc or use make doc_html or make doc_man to only generate the html documentation or the man pages respectively.

The HTML documentation is in doc/html/index.html in your build directory and the man pages are in doc/man.