Manual:Using MediaWiki as a content management system

MediaWiki can be used as a "CMS" content management system, e.g. if you want to create a bliki (combination blog/wiki). Before going this route, you may want to consider factors involved in deciding whether to use a wiki as your website type.

Advantages and disadvantages
Using MediaWiki as a CMS might be an appealing option if you are familiar with the ins and outs of editing MediaWiki and administering MediaWiki installations, but lack the time or inclination to learn how to use other CMS software (such as Wordpress, Joomla or Drupal). It might also be beneficial if you already have some pages written in MediaWiki markup that you want to import into your site.

MediaWiki was designed for openness and mass collaboration, though, rather than for single-user blogging. There are fewer MediaWiki installations than there are other CMS installations, because one MediaWiki installation can often serve hundreds or thousands of users, while typically there is one Wordpress installation per person or several persons. Therefore, arguably not as much attention has been paid to making MediaWiki easy for the non-technically-savvy to administer. For example, MediaWiki lacks the sort of advanced extension management platform offered by Wordpress. If you primarily just need a CMS, and only have limited need for wiki-style collaborative tools, an alternative is to get a CMS and install an extension that will provide those capabilities. See for example the DokuWiki extension to Joomla. There are also some wiki software packages, such as Confluence, Foswiki, SharePoint, Tiki Wiki CMS Groupware, TWiki, and XWiki, that have blogging functionality either built into their cores or available through plugins.

One possibility, if you like Visual Basic, is to combine MediaWiki with vbadvanced, vbulletin, mediawiki, and vbwikipro. Vbulletin allows you to have forums and blogs, along with e-commerce possibilities and social networking. VBAdvanced handles all your CMS issues, add modules, and allow you to integrate all types of pages (such as flash, php, and html apps). Then you can add MediaWiki and the vbulletin bridge, which would be vbwikipro.

Extensions
Some extensions you might want to use are:
 * Extension:BedellPenDragon, Extension:CategoryGallery, Extension:RecentPages — These work together to let you add x lists, new x feeds, and randomly featured x (with x being articles, miscellany, quotes, or videos) by editing articles (i.e. without having to separately update the feeds, as is the case with, say, wikipedia:Wikipedia:Today's featured article). The difference between these new x feeds and, say, Special:NewPages is that you get a nicely formatted description that doesn't cut off at an awkward spot. Also, you can have picture galleries with descriptions that come from the image pages rather than the gallery page.
 * Extension:Semantic MediaWiki - allows you to define and query data from within the wikis pages. You can add data like date, tags, author etc. to your wiki articles and query for the these articles.

LocalSettings.php
Here are some configuration settings you may want to adjust if you're interested in using MediaWiki as a content management system (particularly a single-user CMS).

robots.txt
You may also want to disable certain pages in your robots.txt file for search engine optimization purposes: User-agent: * Disallow: /wiki/Special:Random Disallow: /wiki/Special%3ARandom Disallow: /wiki/Special:Search Disallow: /wiki/Special%3ASearch

MediaWiki:Common.css
Some settings for your MediaWiki:Common.css

MediaWiki:Common.js
Some settings for your MediaWiki:Common.js