Working to make a complete event management system for events especially for Drupal.
Building communities is an artsy science that is a strategic initiative for organizations of all kinds from nonprofit to for-profit. In this webinar, we will remove the mystery of building thriving online communities. We will look at community building best practices from leading community managers such as Jono Bacon of Ubuntu, and will understand how to use these pro-tips to grow and nurture global communities through a case study on Drupal.
Why Should You Attend This?
o To learn how the Drupal community grows and is nurtured
o To learn about the community management best practices
Drupal 8 will ship with a fancy new template engine (Twig) and a simpler theme layer. In this webinar, our speaker will show you some goodies from Twig and give you a walkthrough on how to get started with it.
He will also talk about the major problems that people were facing in working with Drupal 7 and what the community has done to make it better. This webinar will show - in both practical examples and on a broader scale - why Drupal 8 will make peace between backenders and frontenders.
Why Should You Attend This?Read more
Drupal 8 is taking the same path as other MVC (Model View Controller) frameworks like Ruby and Symfony, which makes it easier for developers to make an easy entry. Much of the Drupal code which seemed alien before now seems familiar to developers with experience in other frameworks.Read more
I've made a full project node for the Cream distribution at https://drupal.org/project/cream
I started a new project rather than use aburrows' sandbox since the repo for that has all of core and the contrib modules in its history from before this was using a makefile -- best to start from fresh :)
The -dev release should be packaged soon. See the README for installation instructions. If you want to clone from git, the README also has instructions on how to use the makefile.
What's in the box so far:
- node types and entity types for building a schedule
I've added a basic structure for the CREAM.make file, so what we need to do is add more modules we need for the site. I recommend the structure of modules should go in sites/all/modules/contrib and then any custom cream modules in sites/all/modules/cream/.. The make file is pulling timetable into sites/all/modules at the moment but perhaps we should move this into a cream directory.Read more
I have made a start on the workflow for the 'Event creation Wizard' or what is more like a Dashboard & Wizard.
My thinking is that the system should track the progress and tasks required to not only setup the event but the entire process of the event until the event day.
What I havemocked up (attached) is the way the system could start you off and then direct the organisers into different wizards that would combine to complete the tasks needed for an event.
The mockups are done using moqups.com, so pass me an email address to add more mockups if you wish.Read more
We've identified the following personas for site users:
- Visitor: has not yet committed to anything. They have not created an account or signed up to come to the event.
- Attendee: has signed up to the event by creating an account on the site and (if required) buying a ticket.
- Participant: an attendee who additionally has submitted a session, or is a sprint leader.
- Volunteer: an attendee who has volunteered to help with management of the event, either in the lead-up or on the day.
- Site builder: builds the site for the event.
Here are some of the features we are proposing for CREAM.
The plan is to assemble this list over the next few days and then do a prioritizing exercise (probably with a Google survey; we'll invite votes from the community). This will then help us produce a roadmap showing the order in which we'll implement features:
- Features which form the MVP which should be implemented first.
- Additional feature in order of preference, which subsequent builds of CREAM can add.
- Signup: Site visitors can create an account and sign up for the camp and become attendees.
We talked at the London cream BoF about progressively enhancing CREAM with each build for each successive DrupalCamp.
I think it's worth trying to formalize this a little bit more, and coming up with a roadmap. Successive DrupalCamp site developers could pick one or two items from the roadmap that they're willing to build and contribute back to the CREAM distro.
So, for example, some items could be...
- have attendees create their own customized schedules with Flag module
- have attendees vote on proposed sessions before they are approved
I'm making really good progress with the schedule building system.
This is going to take the form of a contrib module which provides an ECK entity, 'timeslot'.
- the usual ctools, entityreference, etc
This then requires entities to act as sessions and schedules, and takes care of providing custom field widgets and formatters for the entityreference fields that join them up, as well as a big monster timetable building form.
For CREAM's use of this, it'll be:
- schedule nodes; one for each day of the event.
So we need to discuss a roadmap for CREAM and what we ideally want to have in CREAM. I'm proposing we do a Google hangout for this, sooner rather than later. I'm in the process of contacting Drupal event organisers mainly the developers themselves and see what they liked and disliked about their current system and even if they used COD. This will help us work out what functionality we need and what are nice to haves.Read more