Elgg

You are currently browsing articles tagged Elgg.

While comparing software features is important, it is also essential to consider user experience. This post is going to focus on the new user experiences for Elgg and BuddyPress working through first look at the site, the registration process, and the resultant page once one has logged in for the first time. I gave an initial overview of the differences between Elgg and BuddyPress in my previous blog post.

With BuddyPress, a visitor arrives a page that may look like this with a “sign up” link on the upper right hand side of the page.

In Elgg, a first time visitor may encounter a page like the one below. Note that the Elgg landing page has been altered using an index.php override. I feel this is a fair comparison in terms of effort with installation. As you may recall from my previous comparison, the BuddyPress installation required a certain amount of coding, so I thought it would be fair to apply comparable effort to an Elgg installation as a starting point. Note the registration link in the left column.

bpelgg2

Registration

Click on the register button with BuddyPress and you arrive at a page asking you to provide profile information by filling out several fields. The administrator can change or add to these fields making them optional or required. In this installation, I added a “Profession” field. Further discussion of this feature will appear in future posts.

bpelgg3

Next, you are given the option to create a blog or just an account.

bpelgg5

You then are notified to look for an activation email. Once you click on the link in the email, you are given a password.

bpelgg6

Elgg, on the other hand, simply asks for a display name, email address, username, and password.

bpelgg4

Click on Register and you are returned to the landing page with a prompt telling you that you will be getting an confirmation email. Clicking on the link in the mail returns you to the site notifying you of confirmation success. You can then log in.

Logging In

Once logged in, Elgg and BuddyPress deliver you to entirely different pages. BuddyPress brings you to your public Profile page, while Elgg delivers you to your private Dashboard.

Once you log into your new BuddyPress Account, you return to the main page with the options available to a logged in user. Note the gray menu bar on the top of the page that was not visible when not logged in.

bpelgg9

The first time you log into Elgg, you arrive at your dashboard page and prompted to click the edit page link highlighted below. The dashboard is visible only to the account owner.

bpelgg7

Once you click that, you are presented with a set of widgets that allow you to customize your dashboard. Simple darg and drop them into one of the three columns. These widgets can also be configured. On a side note, Elgg’s profile pages function much the same.

bpelgg8

Conclusions

BuddyPress’s and Elgg’s landing pages are strikingly different, especially if Elgg’s index.php file is not customized. No question that BuddyPress’s default theme with the widget customization is more attractive out-of-the-box. That being said, this is not very important as one can install different themes on either platform. Elgg has many free themes available and BuddyPress will have a variety of themes upon release. Discussion of this is really best left to another post.

BuddyPress’s registration page solicits much more information than the bare bones Elgg registration page asking the new user to fill in profile information and to upload an avatar before the registration process is complete. It also allows the administrator to customize the fields in the form. This could cut both ways. Some users might be put off by the steps required to register preferring to enter just enough information to get inside. On the other hand, it would be more likely that users actually provide profile information and an avatar. It requires somewhat more of a commitment to get an account. In the Elgg community site, I have found it irritating that many users have no profile information at all because it is not required. They just leave it all blank.

Elgg, delivers you to a blank dashboard page; whereas, BuddyPress delivers you to the logged in front page. Some have argued that the blank dashboard is confusing and univiting. On the other hand, it does invite immediate action to customize your account with an easy to use widget interface. With BuddyPress, you will need to explre the menu to find more options. Both Elgg and WordPress require a certain amount of exploration once logged in as not everything is immediately obvious.

I will continue to post about the features and user experiences in future posts. Hopefully, these posts will help individuals choose the best platform for their needs. Beyond that, perhaps developers can learn by examining the different interfaces.

Tags: , , ,

The Elgg support community’s access to content has gradually been restored after  large portions of the community site were closed or disabled apparently because of attacks on the core developers. The Elgg Google groups were unaffected other than becoming much busier.

Around the turn of the year, developer Dave Tosh created a group with the intent of discussing improvements to the Elgg community site for developers and end users. The most interesting discussion occurred in the Welcome post.. Subsequently, Dave Tosh has outlined changes to Elgg support:

We have decided to go for a top level elgg.org documentation area that is powered by Mediawiki. This is similar to many open source projects and therefore makes sense as developers are used to it.

At the moment, I am not sure how this is a change. Curverider has used MediaWiki as a vehicle for documentation since the release of Elgg 1.0. MediaWiki has been skinned to look and feel like the rest of the Elgg site which adds unity. Other than that there have been little. Community members still cannot change or add content to the wiki as I am accustomed to in other open source projects.

Groups have been refactored to improve the layout and highlight key groups. I think it is worth sticking with groups for discussion and where there are shortcomings, address them. We have restricted the creation of new groups, but existing groups are still active and owners can now decide if they want forums, page and files as all are optional.

These are positive changes. Highlighting important groups will draw users to where they need to go. It will also discourage the duplication of what is already present. Restricting group creation is also a good idea. This is very similar to how discussion forums operate—the administrator controls the organization of the site. Users generally cannot create a forum.

Integrated google search. We took our cue from WordPress on this one. Using Google search was the fastest way to get integrated search across the three open source tools we use on the elgg.org site (Mediawiki, Elgg and Trac).

The search function in Elgg has been a serious limitation. An integrated search using Google is a great help. I think it might even be better if it searched the Elgg Goggle Groups as well. I also look forward to seeing this as a plugin.

Plugin authors can now decide if they are going to allow comments on their plugins and shortly there will be basic version control which should help make it easier to follow plugin development.

This appears to have been implemented. Plugin authors can now choose to replace older versions when they upload newer versions. Again, this is a positive development. I wonder though, if some implementation could be created that allow users to keep older version available as they may be compatible with older versions of Elgg. [Edit: Cash Costello reports that this is the case.]

An open source project becomes a diverse community of developers and users with vastly different interests and needs. People have varying abilities and skills.  I believe that many constituents may be best served by employing a bottoms up model in which they can become active contributors to a knowledge base. Both FaceBook and WordPress allow individuals to create accounts and edit content on their MediaWiki documentation.

I appreciate Curverider’s moves to improve support for the Elgg community. We are all indebted to the developers (core and otherwise) for all their hard work in making Elgg what it is and sharing it with the world. An open repository for shared knowledge would would enhance Elgg’s success. I’ve enjoyed working with Elgg and look forward to working with it to put together a great K12 social networking platform.

I invite your thoughts on the matter.

Tags: , ,

In the past few days, Curverider has reopened access to many features of their community site. Some functionality has been restored. Group owners have the option of turning their forums back on. It also appears that comments are now available for plugins and templates.

In addition, Dave Tosh has opened a discussion pertaining to the Elgg community asking for suggestions as to how best support Elgg. So far, the discussion has centered on software, but there is much more to managing a community

This is a positive step and helps build confidence in Elgg as a platform. I hope that the Curverider developers take to heart what has been said on this blog and ib subsequent comments.

Tags: , ,

A long sought after calendar plugin for Elgg has been created by Kevin Jardine. This add-on, commissioned by the Royal Society of Architects, provides an event calendar for each group created in the Elgg installation.

Event Calendar requires Elgg 1.1 or higher. The only departure for a standard installation is that the plugin’s directory should be changed from event_calendar_0.6 to event_calendar before activating. There is no configuration—the group calendar just appears in the owner’s block as a link when you are in a group.

cal1

Clicking on the calendar link brings up the following page.

Click to enlarge

Click to enlarge

In the main content area, there are options for viewing the list of events for a given day, week, or month. In addition there is an interactive calendar/datepicker. The large blank area displays the events. Right now there aren’t any, but to create an event, one clicks the Add Event link on the owner’s block

Click to enlarge

Click to enlarge

There are several fields for information about the event. Note the popup calendar for selecting dates. There is no option for a time, so I put the time in the title. Once an event is created the event appears in the main content area

Click to enlarge

Click to enlarge

This displays all the information entered about the event. And you now have some new options in the owner’s block.

cal5

Beyond the options to edit or delete the event, you can add the event to your personal calendar. The entire site’s event calendar can be access through the tools menu of the top bar. In addition, the Events Calendar plugin provides a widget that can appear on your dashboard of profile list the events that you added to your personal calendar.

cal6

Returning to the Group’s page reveals an event calendar list all the events for that group in the main content area.

Click to enlarge

Click to enlarge

One last great feature appears as you return to an individual event. Once you are on an event page, a personal event calendars button appears on the owner’s block. If you click on that, you get a list of each user that added the event to their personal calendar.

cal8

To customize the appearance of the calendar on the page, edit:

event_calendar/datepicker.css

To change messages, spellings, or wordings, edit:

event_calendar/languages/en.php

This is clearly a well developed plugin width a great depth of presence in the installation in that includes, not only group event calendars, but a sitewide calendar, and a widget to display individuals’ event calendars. The ability to view who else has added an event to their personal calendar is also a great addition.

This is an outstanding extension to the Elgg core and goes far in fleshing out Elgg’s functionality. It is currently version 0.6 beta. I wouldn’t be surprised to see further enhancements of this plugin as new version emerge.

Tags: , , , ,

Elgg‘s development continues and appears to be progressing toward its next release—version 1.5. The svn revisions “odometer” has begun moving again this week after a brief break following the release of version 1.2.

Elgg’s roadmap states that Curverrider plans to make major relases every six months with Version 1.5 due in February. Several target enhancements due with this release have already been completed:

  • An Administrative interface for customizing profile fields
  • Metastring garbage collection
  • Log Rotation
  • Additional themes

Scalability enhancements are partially completed. Slated further improvements include:

  • Views and plugin location caching
  • A mobile device view
  • An OpenDD client for syndication, imports, and exports (will this mean 0.9–>1.x migration?)
  • Improved front page layout and submenu system
  • The often requested group deletion
  • Drillable site-wide activity stream

Elgg progress is not limited to the work of core developers. We are starting to see institutional support for Elgg development and customization. Kevin Jardine developed are critical event calendar plugin funded by the Royal Institute of British Architects. A large K12 school district in the US is considering an Elgg roll out with monetary support for the necesssary customization by core developers. Other institutions are beginning to pour manpower into Elgg modifications.

These developments bode well for  Elgg’s future. I plan on continuing to support Elgg through a number of means in the future. I look forward to its implementation in K12 education.

Tags: , ,

« Older entries § Newer entries »