Welcome to Elgg's documentation

This is the place to find documentation on all aspects of Elgg. If you would like to contribute your own documentation please do; we want this to be a real community effort!

Roadmap

From Elgg Documentation

New Roadmap

See also the related forum discussion.

  • strict separation of view and data
    • authenticated feeds
    • feed enclosures for embedded files
    • will need new API
  • error handling
    • currently errors are being hushed, in the ultimate case returning a blank page if an unrecoverable error occurs. a global error handler needs to be in place for catching these events and possibly logging the errors to screen or a logfile
  • general code cleanup
    • clear API and development conventions
    • inline documentation
    • remove the run() function and redefine functionality in API calls
  • better way to add to the head tag
    • javascript loading by plugins on demand
    • css loading on demand
  • file handling
    • more generic way for file handling and storage
    • file API
    • better integration of tinymce with the files
    • multiple uploads, easy embedding in blogs
  • page editor
    • adding pages to the site or at the user level
  • better ways for annotating
    • better ways for persisting stuff like permissions, tags, comments and e.g. file attachments to objects
    • user rating on content - based on a favourites system
  • better, integrated search
    • search API
  • fine grained system messages
    • e.g. notifications on a finer grained level (on individual posts for example), but also more backends: besides email, IM (XMMP), SMS, pigeons (see also RFC 1149 and RFC 2549)
  • admin interface for plugin activation/configuration
    • user interface for user space plugin settings
  • theme portability
  • notifications for all types of events/notification API for use by plugins
  • new theme
  • general improvements
    • flexible sidebar
    • flagged content to be copied, logged and send to the system admin via email
    • community owners to add users to private communities
    • better tracking of comments on discussions you are following
    • user activity to include the number of unread posts from each community they are a member of
    • custom profile fields on a per-user basis, perhaps with the ability to push fields from an administrative service
    • the ability to prepopulate keyword/tag fields
    • refine the widget API
    • IM capabilities
    • import and export of Elgg accounts including resources and relationships based on open standards
    • integrations
      • Flickr
      • Delicious
      • Photobucket
      • Upcoming
  • OpenID consumer and provider functionality
    • plugins exist, which need to get polished and possibly enter core?
  • Atom / AtomPub infrastructure

Back to Development frontpage

Retrieved from "http://classic.elgg.org/mod/mediawiki/wiki/index.php/Roadmap"
Navigation