CMSWhatWeWant

[ CMS20060910MeetingAgenda CMSWhoWeHave CMSWhatWeHave CMSWhatWeWant CMSSurveyList ]

The wishlist

This list contains features that are high on the wishlists of IMCs. As IMCs don't have these features, it isn't a requirement to have a CMS system that has these. However, it is highly desirable that the CMS we choose has, or can fairly easy be extended to have these features.

Name	Description
Logins	In order to prevent people abusively masquerading as another user, it would be nice to be able to register the (nick)name of a poster. This feature might furthermore be employed to allow easy navigation to "more of this user" postings, stimulating open publishing for frequent contributers. An extra aspect of this feature might be to have these (nick)names registered globally, so one registration suffices to have a (nick)name registered for every IMC.
access control	It would be desirable to be able to differentiate between different admins / users with regards to what they are allowed to do. An example usage might be: for a multi-collective imc site, each collective might only have access to change the pages belonging to the collective. As CMSes may implement this feature in widely varying ways, it is extra important to make a good description of the possibilities of the given CMS regarding to functionality like this.
user moderation	In what sense can visitors play a role in the moderation of the site? A CMS may for instance support voting a la \| http://slashdot.org ? .
open editing	Can posters edit their articles after submission?
profile	What possiblities does the CMS with regards to user profiles? This might include a page with the articles posted by the user, a list of their friends and so on
user notifications	Related to the previous feature: does the CMS offer the possibility to contact an author by way of his profile, without the author having to publish his email address in plain sight?
notify moderator button
podcasting/vodcasting	Does the CMS support podcasting/vodcasting? What possible extra features does it have in relation to this?
redundancy (DB content storage)	Given the problems indymedia has with server seizures, we would be much helped if we could find a CMS that can be installed so that "if one machine is taken by surprise out of the network, no imc will suffer downtime as a result". This would typically include database replication, but this is neither necessary nor sufficient.
version control	Does the CMS offer version control on publish content? That is: is it possible to track all previous versions of an article as it's edited?
customisable skins by user	Can users customize the presentation of the site? If so, what possibilities are available?
accessability
xhtml validation
GIS
photo galleries
licensing options
image manipulation
p2p integration
social networking / filtering systems
wysiwyg
tagging:	Does the CMS support tagging? What options are available? (think of searches, the ability to moderate tags, etc)
anti-bot systems like captchas
easier installation	Is it easy to install the CMS using default cobnfiguration values? Do packages exist for the major distros?
cross site search

Other ideas collected outside of meetings

05:43 < a> and what we want is birefly 1. auto updating last comments 2, hiding all

           the comments of an article when the main article is hidden 3 possibility 
           for admins to hide news/comments when they are browsing through the site

i'd like to see very, very easy to use api's exposed to the world at every level of content, beyond just rss. it should be trivial to get and reuse indymedia content in exciting ways. -johm
i'd also like to see a nice balance between crazy dynamic features like network wide tags+social networking+etc. and static replicatability of basic site content. perhaps generation of rsyncable static html with javascript calls to additional services taking place on the client? -johm
Perhaps VoIP too? :) -jebba
Posibility of Multi-node, like estrecho.indymedia.org
Functionality and looks should be easily customizable, adjustable, in- and decreaseable (i.e. optional modules) by each IMC even with little tech knowledge. Patches providing customized, added or removed (configuration changes) should be easily maintainable by each IMC even with little tech knowledge. - alster
Complete support for bi-directional text (both on HTML forms as well as page layout) and uncommon character encodings (possibly not contained in unicode) - alster
User friendly interface and usability on all levels -magduv
An extra aspect of the network-wide login might be include non-IMC sites, for instance using: LID/OpenID/YADIS