Voting starts in March for the Drupal Association Board election.
THIS IS A TEMPORARY OUTLINE FOR THE LIQUID WIKI ENGINE MODULE PAGE. I AM CREATING IT FOR USE WHILE I AM WORKING ON THIS DOCUMENTATION. PLEASE ASSUME THIS DOCUMENT IS INCOMPLETE UNTIL THIS TAG HAS BEEN REMOVED.
Here are the sections that will be outlined in this document:
1) Front Page -
a - Intro
b - Rationale (Why use it, feature comparison to other Drupal functions)
c - Prerequisites
d - Coming Soon section
2) Child - Installation
3) Child - Admin pages explained
4) Child - Special permissions explained
5) Child - Listing of installed modules and submodules and functions
6) Child - Table structure
7) Child - FAQ
8) Child - REAL EXAMPLES
The purpose of the Liquid Wiki Engine Project is to provide a framework for implementing a wiki on a drupal site. The intention is that Liquid should provide the Wiki infrastructure to Drupal rather than specific markups. While MediaWiki format is currently the standard markup for Liquid, the actually focus of the module is implementing features such as freelinking, wiki heirarchy, redirects, and other common wiki features. There are many changes from the first hack. Some of the more important ones are listed here.
The main problem with the old module was that any extension had to be made by patching. Therefore, the most important change has been to define a hook point interface and split out all but the base functionality into separate modules. Today liquid consists of four modules:
* Liquid Base - The base system which provides the infrastructure for wiki name-binding and access permissions.
* Liquid Access - Provides five more permission controls and three access levels that can be defined for each node in the wiki.
* Liquid MoveRef - Provides redirects and references to moved wiki pages (similar to those in media wiki)
* Liquid Filter - Provides the Media Wiki Markup Language filter.
The extension interface provided by Liquid Base consists of three parts
* Wiki API - Allows modules to respond to wiki events (insert, move, remove, update, validate).
* Page Handles - Allows modules to provide page handles for specific wiki id's. This makes it possible for other modules to provide special pages and similar functionality
* Access Controll - A similar interface to the one provided by the node module for the operations "wiki_move" and "wiki_manage".
Update to Drupal 5.1
The code has been upgraded to work with Drupal 5.1. The older version of Liquid has been deprecated and, unless someone is VERY persuasive, no further development will be done on that branch.
This has not been tested thoroughly, but Liquid should now support wiki id's in native languages. If you experience problems with this functionality, turn off "use path module" feature.
Hierarchical Wiki Ids
Liquid now supports hierarchical wiki ids. You should turn on "set breadcrumbs" in order for this to be of any significant use.
It has been suggested in various places on Drupal.org that Drupal already has the ability to imitate a wiki with it's core features. ADD LINKS FOR THE FOLLOWING LINES Typically this involves a cobbling together of things such as the Book, Freelinking, Pear Wiki Filter, and various other modules. Liquid has everything you need for a standard wiki interface all in one place. Any kind of node can be inserted into the wiki. It does not rely on any specific wiki markup language. It also offers access control above and beyond Drupal's standard access control. Liquid is the closest thing that Drupal has had to date that is a one stop, one click solution for sites needing wiki's.