This page contains ideas for the RemixProject web sites. See the WebSiteTODO page for particular tasks that you can do.
Urgent bugs
- Restore the link to "personal information" in the edit account part (used to be a tab, now gone because we had to hide the menu)
- Search doesn't pick up nodes well at all - try searching for text in node titles to see what I mean
Change the page for "formatting guidelines" to contain the same text as is in the manual - http://www.remixreading.org/learn/manual/blog
Small changes to site
- Show automatically generated thumbnails of images and videos if the artist hasn't uploaded their own (with imagemagick)
- Make more use of left hand side of screen, especially on homepage (Benmroth)
- Have a featured artist every week to promote creative people. Have a link at the bottom of the section called "Become the next featured artist" to encourage people to submit new work, a dialogue about themselves and a picture. (Benmroth)
- Have a "show current members online" with chat/interactive features.
- A chatroom - more interactive (benmroth)
- RSS feeds embedded in the pages so they can be used by aggregation tools like aKregator (including the title, link and teaser / description)
Editors picks (with links at the bottom of the list on front & get content pages)
Latest additions (with links at the bottom of the list on front & get content pages)
- News (with link at bottom of news list)
- Be able to contact other members of Remix Reading directly through the site. i.e. on a members page, have "email this member". This would lead to an email form - therefore not giving peoples emails away. This would help members collaborate much more easily, and also facilitate members meeting up.
Big potential changes to site
Each list is vaguely listed in terms of priority...
Network capabilities
- Allow uploaders to select sources from other remix* web sites, e.g. add a work to Remix Brighton but select a work on Remix Reading as a source
- Mark these sources differently to make it obvious to visitors that it's an inter-town remix
- Have an aggregation system to show latest, highest rated, editors picks, etc. across whole network
Files and submission system
- Cater for alternative upload methods, e.g. ftp, webdav, etc. to alleviate problem of large files going through PHP/Apache
- Serve files through Drupal, and enable a monthly bandwidth limit
- Mirror files on ibiblio to save on bandwidth
- have Remix Reading radio streaming using m3u files
Tag music with CC tags in id3 - http://cctools.sourceforge.net/
- Add RDF CC licence info to each upload/article
Refactor Drupal's submission system to reflect http://www.remixreading.org/rfc/add-content.html - huge and ongoing work in Drupal
Ratings and finding artwork
- rating system for uploaded works - e.g. 5 stars
- family tree viewing of files - so you an see where a file has come from and where it will go
- Finer grained browsing methods. I was thinking in lines of: (Ber)
- If you like A, you might like B.
- If you feel Happy you might want to look at C and D
- If you are looking for an upbeat drumloop go for E
If you like ?FamousBritney listen to ?UnknownCreativeCommonsBlondie.
- * This could be relations set-up by the artist
- * This could be generated from user playlists (I set-up a playlist with works X, Y and Z... you look at work Y and it says something like "Users who liked this also liked: X and Z"
- Shadow taxonomy would be to have various category groups besides the Genres. Genres, Artists and Mime types (video/AVI, music/ogg, mp3 etc) should always be the main browsing methods. These should be kept simple and with a minimum of choices
Subscriptions
- Add Subscriptions:
- notification of updates of:
- A user. When he posts notify subscribed users
- A work. When a remix, or remix of remix etc is added notify subscribed users
- A genre. receive all updates in a genre.
- A work. When a remix, or remix of remix etc is added notify subscribed users
- notification is performed by:
- RSS Feeds per item
- Email (batches)
- My Personal subscription page showing all updated subscribed items
- A user. When he posts notify subscribed users
- notification of updates of:
Events
- Events pages - a list of events, split into upcoming and past events.
- Past events to be archived.
- Each event has a title, photo, venue, date+time and brief description.
- Let users in a group (editor?) add and edit events
- Past events can have nodes attached to them for photos, reviews, etc.
- Let users in another group (authorised users?) attach nodes to any event
- Venue field should link to a page containing information on the venue:
- Name
- Photo/logo
- Address and map
- Tel/fax/e-mail
- Can also include brief list of upcoming events at the venue
Misc
Add "more" links to artist page listings. http://drupal.org/node/12934
- incorporate blog into text so it is a text genre - not completely necessary
- automatic resizing of user pictures