WhyJustRun / Core

Authentication, IOF XML APIs, and cross-club pages
5 stars 4 forks source link

Nested event support #21

Open russellporter opened 10 years ago

russellporter commented 10 years ago

It would be great to be able to have a parent event and child events. The parent event would link to all the child events and show overall information, and child events would be very similar to existing WJR event pages.

russellporter commented 10 years ago

Feedback from Adrian on the first prototype: I think it is quite good! I do think having a multiple-event capability is important.

The “myO” interface was a bit like this, so I like it ;-) in myO there were six things on the front page:

Event Info – this is a calendar showing all events (e.g.: BBQ, races, model events, etc). Each event is “clickable” to go to the event page. This is nicely done in your prototype. Start lists – this is a start list display, with drop down at the top of the page to select the race for the start list. Start list has various display options (by club, by class, by name, by time, by “favourites”, etc). This is kind of cool and very useful for bigger events (such as COCs). Relatively simple to add this I think, and there are lots of places in the UI where it could go. It is nice to have it on the main page, since it is one of the more important bits of information for a big event. Results – same as “Start Lists”, but this time to display results. Again, good to have on front page since it is so important. It is also nice to put start lists & results in a central place (I.e. NOT just with the actual race) to make it simpler and faster to find News – that is pretty much covered off with what you have designed already Map – this is a map showing the event locations. You already have this. More – this page has a list of links to more information. This is customizable by the event organizers. It could include stuff like Accommodation, Safety, link to online registration, and other special notes. I use a special XML tag to identify the title, and then just a bunch of HTML for the page content. I think the IOF XML data format has quite a lot of good stuff in this area, as myO is based a lot on that format. I think it would be good to try to use the XML format (and they’ve been very accommodating in expanding it to meet my requests in the past).

So, in a nut shell, I think this prototype matches my way of thinking about this problem very well. It is really tidy and compact, and I think could easily tie into third-party tools if that were appropriate (like, is there any point to myO anymore, since WhyJustRun does pretty good job on mobile device)

russellporter commented 10 years ago

First (really rough) prototype

whyjustrun nested events