Page last modified 18:41, 8 Sep 2008 by RoyK
Table of contents
No headers- Collaboration:
- Friendfeed, Facebook News Feed ... there's no reason we couldn't sexify "Recent changes" to improve content readability
- example: allow different view modes - attached files - added comments - LET people add comments to a page about a revision!
- something to consider: what "is" a revision? (comments? tags? files?)
- tagging user page makes them a "friend" - watch list == recent changes personalized
- Friendfeed, Facebook News Feed ... there's no reason we couldn't sexify "Recent changes" to improve content readability
- Permissions - this is crucial - as we target more SMBs (<50 people) who want granular control, we have to reconsider it all. Accessmaps - might be a good idea. Technical: Drop roles and restrictions as masks - work with the flags directly. Users have no permissions, until assigned to a group, which has a permission mask.
- User namespace: Do what the hell you want - Max
- Custom namespaces: (Or allow Special: and start converting things like "Top Contributors" and "Top pages" into DekiScript) - Damien
- Push notifications (Events/XMPP) - allow appications to be "notified" when changes occur - lets you do things like AIM notices, email notifications, Twitter posts, WordPress posts ...
- Internal feature: Watchlist (takes advantage of this)
- Required feature changes: Subscribe to a whole tree, comment on a change
- Internal feature: Watchlist (takes advantage of this)
- Tag page
- What links here
Images 0
You must login to post a comment.