See also: WikiSpace, WikiAsPim, DigitalPalace, WikiToDrupal
Thoughts on what I'd like my DreamWiki to be. Currently I use MoinMoin but PhpWiki and PikiePikie (note that PikiePikie developement appears to have gone down a (partially?) commercial route) are the two that are closer to actually doing what I want.
Random thoughts which will be organized later ...
Arbitrary page output format so you can output your page in RDF/RSS or even raw wiki markup (who knows what we'll think of in the future). The idea would to be able to use an RSS version of RecentChanges or CategoryCategory as a slashbox in a weblog.
- I'd like to be able to include other RSS feeds, polls etc in the default template (though this is easy enough to do with the templates, it might be nice if it was configurable via the web).
- I'd like email notification of page changes. And a different variation on this, I'd like a tag (like the "minor edit" one) to be availabe only to certain users which means that when the page is saved the entire page contents are emailed somewhere. the reason i'd like this is because i run a mailing list and would like to have each message have a wiki page where people can comment, fix, add to the story i send out. rather then send the email and have to copy it to the wiki, it would be nice to just add it to the wiki and click "send email to list" or something like that. I supposed this probably involves another output format so that it looks okay in email as HTML doesn't belong in email and wiki markup probably wouldn't be that friendly.
- Page comments. I'd like the ability to embed a comment it the wiki source. This would be for comments which might be important to another editor but not to a reader ... it could also be used for storing page meta data in the page.
More on this: page parts visible in different modes (editting, RecentChanges, search etc.) -- AS
- Category meta data so you get a drop down box for categories and topic on the edit page, and I'd like tokens which allow that information to be represented in the page template.
Be more verbose on the 2nd (token) part, I don't get it. -- Jürgen
- I wrote this a long time ago, but as I recall I was meaning two things, both assume that HTML page layout is generated from am template in some way. The first was that meta data stored in a wiki page (say as a comment like ##meta:category:Software) could be accessed with in page template by a variable ($meta_category). The other thing that I'd request now is that you could use Moin macro's withing page templates as well (say for a random quote to appear somewhere in the page other then in the wiki page itself). -- Adam.
I'd like the ability to attach files to pages, have per user quota's and to then be able to refer to those images via some InterWiki mechanism. Maybe something like local:MyPage:picture.gif.
- A wiki photo gallery, this would require the ability to attach files to wiki pages and then you would write a plugin which would parse all of the attached images and create a thumbnail layout on the page. If you click on a thumbnail then a picture would pop up in a seperate window with the full size picture in it. Other more clever stuff could also be done (like have a picture per page and then figuring out some way to link multiple pages together in an album, this would allow pictures to have comments attached) but that would be a start.
MoinMoinGallery is a simple implementation of a wiki based photo gallery by SimonRyan. -- Adam.
- Other useful plugins like a calendar and spreadsheet plugins which work like mentioned here:
http://phpwiki.sourceforge.net/alpha/index.php/WikiPlugin
BROKEN URL - i'd like the ability to lock a wiki page but to still allow comments (comments similar to the nbtsw wiki).
- i'd like the ability to use a wiki as a pim and to find someway to store all my email, contacts, appointments, etc in my wiki and to sync it with my palm pilot.
an implementation of KeptPages
- Some soft way of controlling who can edit a page. Based on some form of karma/mojo/gravity or maybe how long it's been since they created their account. Basically the idea is just to make it harder for trolls to do damage.
- Weblog integration. RSS output would be one way, another way would be to support shared authentication schemes (like the emerging jabber/xml-rpc cooperation that's being discussed on drop.org) or the story syndication stuff that's being discussed in various places (eg. allow a wiki page to be a story in a weblog).
- Per user and per group authentication to control who can read/edit/lock etc pages. Twiki does a pretty good job of this but the way it implements it feels clumsy to me.
Sub-wiki's. This could be useful for integrating other data sources or the WikiAsPim idea (eg. http://localhost/?contacts/15034445555 where contacts is the sub wiki and 15034445555 is the page name). Sub wiki's could have their own RecentPages page and maybe other cool stuff.
MidnightMover already has something like sub wiki: all registered users are granted a realm of their own ({personal:usernam}). Pages that are placed in this realm are not visible to other unless the owned decide to put in into some public realm or change the security policy of {personal:}. Though this solution is not perfect - if one wants to make some pages visible but not editable and others neither visible nor editable he should ask admin about one more realm for this. Now we think that allocating two realms: {personal:} and {public:} per user will be more convienient. --AS
- Not sure if it's feasible but maybe use CVS as the backend and try to take advantage of CVS' ability to automate merges.