wikifier is divided into several components, each built atop the previous. This allows it to be used either as a wiki library or as a standalone program.
The Wikifier package includes the most basic low-level functions. It provides the minimal functionality for parsing wiki source files and generating HTML. This is not to be used directly; instead set up a wikiserver or use one of WiPage or WiWiki directly from code.
The wikifier package is divided into several subpackages:
Formatter - Translates formatted text such as bolds, italics, and links to HTML.
BlockManager - Dynamically loads and creates blocks.
Block - Base class of all blocks.
Element - Represents a single HTML element.
Elements - Represents a group of HTML elements.
Utilities - Provides convenience functions used throughout the software.
WiPage (Wikifier::Page) is the most basic interface to the wikifier. As the
name suggests, a Wikifier::Page object represents a single page of a wiki.
Usually it is associated with a single
.page file written in the
wikifier language. WiPage utilizes the wikifier package to
generate HTML from the source file.
WiWiki (Wikifier::Wiki) is an optional component of wikifier which each WiPage is independent of. This class provides a full wiki manager featuring caching, image generation, category management, templates, and other components of many wikis.
Wikifier::Wiki is further divided into a few parts:
Pages: Generate and display pages.
Images: Generate and display images.
Categories: Generate and maintain category files.
Models: Generate models.
Revision: Wiki revision tracking.
Wikifier::Server implements the wikiserver, a program which serves wiki content dynamically. It is not a web server. Instead, web servers communicate with it via a UNIX socket. This makes it very portable (independent of any specific web server's module APIs), and it allows the wikiserver to perform operations independent of the web server.
In the past, WiWikis were queried directly by Perl modules running on web servers. The new wikiserver is a much better solution because it allows the web script to be written in any language. Consequently you can use any template engine with Wikifier.
The wikiserver also features automatic precompilation and image pregeneration. In other words, the server listens for changes to wiki source files and compiles them on the spot, generating images in all the required sizes. The result is a much faster page load, since the WiWiki never has to generate pages on demand as they are requested.
In addition to autocompiling and serving wiki pages, the wikiserver features write access authentication. This allows frontends such as adminifier to commit changes to the wiki directly from a web interface.
One wikiserver can manage any number of WiWikis.
For each wiki, you will need to write a WiWiki configuration.
Once your wikis are configured, write a wikiserver configuration.
Set up a web script to connect to the wikiserver.
Run the included
Wikifier::Server is not a web server. You have to link your web server to it with some sort of script. wikifier comes with some programming interfaces to do this. They are located in the interfaces directory.
These connect to wikiservers in order to serve content via HTTP.
These executables, included in the wikifier distribution, make it possible to use wikifier as an independent program rather than a library.
Reads the provided wiki page source file, spitting out the generated HTML to STDOUT. Warnings and errors are written to STDERR. Exit status is nonzero on fatal error.
Runs a wikiserver.
Connects to a wikiserver with an input prompt. This is only for testing so you can see how the wikiserver fulfills requests.