![[Home]](/static/logo.png){kind=logo}
Features of the user interface, changing how the content is presented, how the site is navigated, how the editor works, what additional controls are available etc.
A list of links at the top or at the bottom of the page, telling users how they got here, and how they can go back to where they were before.
A way to filter the recent changes by user, part of a wiki, or other rules. In other words, search in recent changes, or see recent changes in search results 
Visitors see a simple user interface, optimized for people who follow a link or two, but are not going to read much, edit pages, etc.
Instead of editing conversations like documents, build threaded conversation support into the WikiEngine. Comments are added with “reply to this” buttons, and appear in a hierarchy of comments. Like Slashdot, Kuro5hin.
See MeatBall:DigestedChanges for background.
With “Insert Submission,” you can easily put text into a wiki page at a particular spot. For example, suppose you just want to add a comment at the end of the page? With insert submission, you don’t need to hit “edit,” and roll the page down to the bottom. Rather, you just put your text into a little box, and punch “submit.” The text is automatically put into the page at the bottom.
Rather than giving an entire page to the user, allow the user to edit just one small part.
Besides every engines choosen (more or less WikiMarkupStandard compliant) markup, some may choose to support foreign engines TextFormattingRules.
2 (or more) people can simultaneously edit the same wiki page. They see each others edits (and their own edits, of course) in real time.
What’s usually most frustrating for users to edit is tables, because the larger a table gets the more lines it wraps in the typical edit box. For things as large as our TableEngine comparison table this gets really a mess.
Therefore a specialized PartialPageEditing feature for tables makes sense, but it was in fact only a poor mans version of a full blown WysiwygEditor.
If TrashCan were implemented, then “delete page” would be easy to undo. (Making things easy to undo is generally a good thing – this helps people CommunityWiki:BeBold, and reduces the “are you SURE?” dialogs and other annoyances that tend to grow around things that cannot be un-done).
The idea of a WikiWhiteboard is to expand the wiki technique to at least visual images.
What you see is what you get. Edit wiki without a special input form; Have a graphical user interface to editing the text.
When browsing the wiki, users can edit a page simply by double-clicking on it (especially useful for long pages, if you don’t want to scroll all the way down).
A single and simple markup to inject text/content styling with already well known syntax and all possibilites from CSS style sheets.
This wiki feature displays external links differently than internal links (or other links like InterWiki InterLinks).
The idea is to segregate the WikiKM:DocumentMode and WikiKM:ThreadMode views of a page.
User can hide and show fragments of text while reading the page.
Footnotes are additional notes placed at the bottom of a page, and associated with some place in the text of page using a symbol like “*”, “†” or a superscript number or letter.
Each page can control how it is formatted, particularly which CSS stylesheet to use. This might also include changing images etc. to “brand” a page.
On RecentChanges, the page that was changes is displayed, and the time of the most recent change. However, it would be useful to have an icon to let the user know when else that page was changed; has it just been changed this once; has it been changed a lot in the last few days, and then not for awhile? has it been changed frequently and continuously for the past few weeks?
Leave some room on the pages for putting various additional information, extensions and links for additional actions.
Features that allow you to organize and annotate the content of wikis or the work done on the wikis.
Allow readers to look at the original WikiText source of the page
Make the characters used for markup visible at all times, not just in the edit mode, but also when the page is rendered.
Everyone can see who’s visiting the site, what pages they are visiting, more or less as it happens (or, within 10-20 seconds, given HTTP).
Certain dynamic elements of wiki pages can make them impossible to cache. There may be however a way to work around that.