...
An event creation page, accessible through the "Create an event" tab in the menubar, contains text boxes for all event information: title, location, time, tags, description, other administers, and comment enabling.
Analysis:
The identifying feature of this design is the representation of events as a tag cloud. This cloud has visibility pros and cons: on one hand, it makes it very easy to see what type of events are around and how populous these events are. After clicking a tag, the user is shown a list of events that fall under that tag. However, in this design there is no way to see all events or sort by location or time. Efficiency takes a hit as well, as a user would have to click through multiple tags if, for example, they wanted to see all events happening in the near future. If we will accept this tradeoff depends on how the user will use this application: do we expect them to look for events based on activity or proximity? Of course, this tradeoff can be alleviated by adding the functionality to list all events, at the cost of simplicity.
With short instructional blurbs (on the order of a few words) around new or confusing features, the learning curve for this application can be minimized. Furthermore, the user is free to click around and learn as they go with very little risk of catastrophic failure. All editable fields require a definite click of "Save" to take effect; there is a "cancel" option for everything editable.