Manage your personal information space with Midgard

CMS: Midgard

not scheduled

Description:

Social web services like Flickr and del.icio.us provide new ways to work and share data with others. However, they also mean that your data is spread around dozens of services, companies and servers.

Midgard can be set up to act as your personal information hub, synchronizing your content with the various Web 2.0 services and displaying them in your own style as a mashup. This means your content can also be secure in a server you control.

You can connect the data from different services together and enrich it with data produced with Midgard's own components. Consider for example having the following play nicely together:

• Blog entries coming from an external blog service or Midgard itself
• Bookmarks coming from del.icio.us
• Photos coming from Flickr
• Videos coming from Youtube
• Status messages coming from Twitter
• ...all connected with geolocation data coming from Plazes and shared via RSS feeds and Microformats

In this session we look at how such a personal information space can be set up with Midgard, and how new functionalities or data connections can be developed for it.

What is Midgard?

Midgard is a venerable free content management system initially released in 1999. Midgard's approach to the LAMP architecture differs quite much from other PHP-based systems in that the CMS is built on top of the GNOME libraries written in C. Every content object accessed via the PHP or Java APIs is first a GObject, and the libgda database abstractor is used for all persistent storage.

Midgard's site management interface is MidCOM, a component framework that allows building new websites with a Lego brick model where you create folders and assign components to handle them.

MidCOM components share an object-oriented infrastructure that provides easy way to build plug-and-play web applications with a common set of UI conventions, configurability and internationalization.

Lead by: