Recently Added/Edited Solutions
Pretty Tables (Rating: 1, Comments: 1)
A very pretty table layout that I thought I might share with you all.
Custom Page Title (Rating: 0, Comments: 2)
In a wiki that I'm a part of, we have very little control over our page titles. If you have a similar issue, the following code should point you in the right direction to create custom titles that can utilize WikiDot text decoration such as colour, weight, and italics.
Hide Tags (Rating: 5, Comments: 2)
The Tag Cloud module does not allow for the hiding of specific tags. This CSI allows you to specify which tag names you want hidden up to 99.
Image Box (Rating: 21, Comments: 24)
One of the common desires of the typical Wikidot user is to easily add a caption or heading to an image. Furthermore, some users would like to easily fancify their image. However, the only way to truly do this is to make a grueling table every time. This CSI allows for a very simple and easy method to insert images, add captions to them, apply headings to them, apply a float, and adjust width.
Multicolumn Layout (Rating: 84, Comments: 26)
OK, so you want a multicolumn layout. Unfortunately there are no special wiki tags for multicolumn layout but the result can be easily achieved using the [[div]] tags and adding CSS style to it.
Extended NewPage Module (Rating: 14, Comments: 42)
Quite similar to the built-in NewPage Module, this snippet provides a way for you to create (or jump to) new pages.
404 (Page does not exist) Redirect (Rating: 6, Comments: 15)
Note: as of the 19th November 2012, Wikidot has implemented a full solution which no longer requires this snippet. View their solution here.
Custom HTML Blocks (Rating: 1, Comments: 1)
Per-User CSS (Rating: 5, Comments: 2)
The basic purpose for this technique is so we can apply CSS rules that override some default CSS settings on a per-user basis. For the purposes of this article, we'll create a couple of CSS classes that will hide data for all users by default. We'll create 2 classes — one for hiding block elements and one for hiding inline elements. Then, we add the CSS for our default state to the nav:side page (would also work with nav:top)). We'll also add a ListUsers module that will render the CSS to override the default for individual users that we specify.
iframe Redirect (Rating: 3, Comments: 4)