Being pathologically nitpicky about details, I tend to refactor my personal homepage very often. To do this, in the past I used to go through tedious FTP sessions or to hack my changes through the shell.
Since I started to work with wikis I realised how effective a wiki engine can be to invisibly power a website. In this post I’d like to share some tips on how I do this.
As I contribute to the development of the open source wiki engine I refer to in the following examples, this is obviously my software of choice (hint). There is however a range of excellent free software you can use to this aim (provided they have good ACL support and allow you to easily modify the look and feel of the output via CSS, as I’ll show later).
Let me first clear one major confusion about what wiki software is for. One common misunderstanding about wiki engines is that they can only be used to run actual wikis (or web-based collaborative projects such as the Wikipedia). Wiki engines are, on the contrary, simple and flexible tools for maintaining and managing different kinds of non-wiki websites, without bothering with FTP sessions.
The following are common sources of misunderstanding about wikis that typically blur the distinction between a wiki as software and the function of a wiki:
- anyone can edit the content of a wiki;
- wikis look wikish;
Both arguments are false. The truth is that editing privileges in most wiki engines (with some flagrant exception!) can be set on a per-page basis through Access Control Lists. You can then easily restrict read-, comment- or write-ACL for a specific page so that no user other than you, a specific user or more users can access the page.
As to (2), wiki-related features typically include: recent changes links, login links, last edit information, last author information, history/revision links and comments. A simple touch of CSS is sufficient to hide all this information from graphical browsers (not from crawlers and text browsers though, if you want to do this you will have to actually modify the page template!).
For the actual details on how to configure your wiki to enable ACL and hide unnecessary elements from graphical browsers you can read this tutorial.
Here I would just like to suggest three aspects that make wikis a fantastic solution for fast and hassle-free content management:
- they allow you to edit and modify content at the speed of light;
- they allow you to easily embed all sort of contents in a page;
- they allow you to set granular access privileges for specific pages, which is a very powerful solution for collaborative work with colleagues and coauthors;
The screencast below should give you an idea of how easy these three tasks can be made using a wiki.
I hope this is a convincing argument to show the power of an invisible wiki and I look forward to your comments and feedback.