Extension:Wikilog

Wikilog enhances MediaWiki with some common blogging features, making it a wiki-blog hybrid. There are many names that are used to represent this concept: wikilog, wikiblog, bliki, etc. (refer to the Bliki article on Wikipedia).

Wiki pages are configured to act as blogs, which are called "wikilogs". Just like blogs, each wikilog contains a number of published articles, with the most recent ones displayed on the wikilog main page in reverse chronological order.

One or more custom namespaces are configured as Wikilog namespaces; pages created directly in these namespaces become wikilogs, while subpages to these pages become wikilog articles (blog posts) and are listed automatically on that wikilog's main page.

The extension provides the extra functionality for wikilogs and wikilog articles. Wikilog articles inherit all the usual wiki functionality, like wiki syntax, edit history, page categories, talk pages, etc. Among the features added by the extension are: automatic listing of articles, setting of article authors, handling of article comments, generation of syndication feeds (Atom and RSS) for individual wikilogs and for all wikilogs of the wiki, etc. For more information, see the full list of features.

The philosophy of Wikilog is not to just make a blog out of a wiki, but to combine both concepts. Unlike most blogs, wikilog articles can be collaboratively written and published by multiple users. Talk pages of wikilog articles provide a simpler interface for commenting than standard MediaWiki talk pages. It is similar to most blog software, with the addition of discussion threading.


 * Project home @Google code
 * Users mailing list

Requirements
In order to use Wikilog, the following components are required:


 * MediaWiki 1.18 or higher.
 * A MySQL database backend.

The following components are recommended:


 * Extension:ParserFunctions

Installation


Download the extension and install it as, relative to your MediaWiki installation directory. You may checkout the latest version from the Subversion repository in this directory, or uncompress one of the zip or tgz archives provided and rename/symlink the directory created. Note: The directory name must either have that name, or  must be set to the proper path in order for the extension to reference stylesheets and images from the extension directory.

Backup your database and local configuration, it is always a good idea.

Add the following lines to your LocalSettings.php (replace, with the first even-numbered namespace greater than or equal to 100 available in your wiki): 

Run the update.php script in order to create or update the tables used by the extension. Note: This script needs to be executed every time the extension (or MediaWiki) is upgraded.</ul>

</ol>

User documentation
User documentation is included in the extension package in the  directory. The documentation is released under a Creative Commons license, and can be imported to the wiki, so that users may access it directly from the wiki. Currently the documentation is available only in English.

You must run the  PHP script from a command-line shell in order to import the documentation to your wiki. Example:

$ cd /path/to/mediawiki $ php extensions/Wikilog/maintenance/wikilogImportDocumentation.php

This will import the documentation pages and images to your wiki, and it can be accessed from  .

The documentation is maintained online; you are welcome to contribute!

Examples of use

 * Elena & Fabrice's Blogs
 * halt and catch fire - Wikilog: Test
 * I ask questions - Blog: Observations (since March 2009)
 * pika - Blog: Recipes

Quickstart

 * 1) Create a Blog:My_blog_name page, with any introductory text for your blog (if you used another namespace above instead Blog: use that one)
 * 2) On your blog front page you will see a new "wikilog" tab to start interacting with
 * 3) There you can find the field: "Create new wikilog article" (see 1st picture below)
 * 4) Create with that a post on your blog (see 2nd + 3rd picture) (don't forget to sign ( --~ ), otherwise it will not be published and stays as draft)

Note: It is strongly advised to refer to the detailed documentation too.