Skip to content

quicksilver/manual

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Quicksilver Manual Source

These are the source files for the online Quicksilver user manual. Use MkDocs to build a site from these files.

Working Locally

Editing this manual locally is relatively easy. You can just edit the files like you would any other Markdown without installing anything.

You can optionally install MkDocs to see a live preview of the site as you work. To use the latest release of Python and avoid installing packages system-wide, I recommend installing Python from Homebrew and creating a virtual environment.

$ brew install python
$ cd <your directory for projects>
$ git clone <your fork of this repo>
$ cd manual
$ python3 -m venv venv
$ venv/bin/pip install -r requirements.txt
$ venv/bin/python plugindocs.py
$ venv/bin/mkdocs serve

This will run a web server at http://localhost:8000/. The site should reload automatically whenever you update content or configuration.

Be sure to review the Style Guide (included in the manual) before starting.

Updating plugin docs

Plugin docs are automatically pulled in from the plugin packages. To generate them for the latest QS build, run the plugindocs.py script:

$ venv/bin/python plugindocs.py

Because of the lengthy download, the plugindocs script will keep a local cache of the plugin info from the qsapp.com site. If a plugin's documentation has been updated, but QS has not, you should run the script with the --fresh option to overwrite the cache.

If a plugin has been removed, you may also want to add the --clear option to remove the old generated documentation.

Developer notes

  • When changes to the supported OS versions are made, these should be reflected in the SUPPORTED_OS_VERSIONS constant in pluginsdocs.py.
  • Check --help for the full list of options.

Updating the Live Manual

The manual repository has been cloned into /data/manual.

MkDocs has been installed into a virtual environment in /data/manual/venv.

Publishing the latest version should be as simple as

$ cd /data/manaul
$ git pull
$ venv/bin/python plugindocs.py
$ venv/bin/mkdocs build

Releases

No releases published

Packages

No packages published

Languages