Events

trying debut events as kit compliant solution

Rethinking this. I think a limited event system would be handy (a list of upcoming events) but a full calendar system seems like overkill. Something that just stores 3 fields - what, when, where.

As it is currently listed in the issue description, no. The only thing I'm considering including is "Upcoming and archived events", and this would most likely be bundled up with the blog feature as a Date/Date API field. Any extra functionality with calendar, ticket sales, event feed, facebook/twitter integration would make more sense as a separate "Event" feature.

After having done a few Personas, and working through the design drafts, it looks like events will be included after all as a separate content type. Still very basic but something that can be expanded upon by others if need be.

Something like this?

Proposed Event content type fields:

What: [title]
When: [date field]
Where: [text field]
Details: [textarea]

since a contenttype alone wont be enough, i will repeat my proposal/question:

what would be a reason not to use an existing app (e.g. http://drupal.org/project/debut_event) ?

@discipolo
Have you tried out Debut_Event? It might be a fine drop in replacement with some additional form altering. Additionally it seems to share many of Pushtape's dependencies.

@gusaus
Interesting, but don't know much about this project or its author.

@zirafa
as i said in comment #1 i tried it.

@discipolo
I understand you've tried it and are proposing it be included. Can you provide some feedback about your experience with it?

well, what can i say. the feature requires the following roles:
- administrator
- contributor
- editor

these roles are what the debut feature defines which is why its reccomended.

apart from that it seems to me they succeeded in creating a kit compliant basic drop-in event calendar solution.
i havent run into any problems so far and cannot see a lot i would do differently.

ical config, archived events, pushing events would have to be adressed seperatly (not included in the basic feature)
- and ticket sales belong into a different issue (commerce)

@discipolo
You mentioned above that an event content type would not be enough - is it primarily the calendar functionality you are talking about? We can greatly simplify our work here by just displaying upcoming events in a table or list. By "work", I mean having to theme the calendar display(s) for any included themes, which is not the most fun thing to do.

See: http://www.drupal.org/project/pushtape_events