Peakium Documentation Viewer
Peakium Documentation Viewer is built to display multi-format documentation in a beautiful presenter. It is built to require no maintenance. It can version track documentation, thus making it easy to maintain and update documentation in git repositories and archive files.
Warning: require(/path/to/documentation/viewer/vendor/autoload.php): failed to open stream: No such file or directory
The documentation viewer requires Composer to work. Install composer and run composer inside the directory. Composer will download and install all required dependencies in the
$ composer install
You need to create the file
config.json and add the appropriate configuration values. Use
config.json.default as example.
You install (and update) the documentation files by running
$ php bin/install
This command will download and install (or update) from all documentation URL's specified in the
documentation key in
config.json, into the directory
||The base HTML page title.|
||The layout directory to use,
pages key consists of a directory with one or more page(s). The order of each page in the configuration, will be the order they are displayed in the sidebar menu, including the section.
The page can contain following parameters:
||The title for the page, displayed in the menu.|
||The section the page should be categorised in.|
||The type of documentation.
||The location of the documentation. For format
Markdown specific values
||The file to load first in a documentation directory. Default is
||The extension of the documentation files. Default is
||The depth that a markdown file should display. When not reaching maximum depth the documentation viewer will include any subsequent linked file in the same page, in the order they are found.|
documentation key consists of a directory with one or more documentation location(s). They are used to download and version track documentations. The format are as below:
The directory-name will be the actual name that the directory will be installed in under
docs, and this is also the
reference value for the
You can add custom controllers in the controller/ directory. Read more
The custom controller will be loaded first, thus if you access
http://localhost/my_controller_name/ it will try to load the
MyControllerName class first (filename would be
my_controller_name.php). If no class or file is found, the documentation viewer will try find the appropriate page in the
pages key of
Layout can be modified in
view. The best way to make your custom layout is to create a new directory in
default is used as an example layout.
Any assets (images, css, etc) can be added in
public/assets directory. This directory also contains a
default directory as example assets.
- PHP 5.3+
- Git for git documentation