You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behavior:
OSEM has no support to tell you what the currently happening events are
Expected correct behavior:
It would be great if this were supported.
Other information:
It seems pgconf and my fork (snapcon) have both created a similar feature. Is there interest in having something in OSEM main?
The way the Snap!Con app works is that I have the events in a few places: a side element on the conference splash page (controlled by a setting on the splash page model), and also a right column on the proposals#show page. I originally built a dedicated schedules#happening_now route but I'm not sure the full page is necessary.
Our version of 'happening now' turns into 'upcoming events' if there's no currently active events, so at the end of the day you see what's going on the next morning.
I think it was a big improvement to our event this year over the previous year, especially the front page links.
The text was updated successfully, but these errors were encountered:
I'm submitting a ..
Current behavior:
OSEM has no support to tell you what the currently happening events are
Expected correct behavior:
It would be great if this were supported.
Other information:
It seems pgconf and my fork (snapcon) have both created a similar feature. Is there interest in having something in OSEM main?
The way the Snap!Con app works is that I have the events in a few places: a side element on the conference splash page (controlled by a setting on the splash page model), and also a right column on the proposals#show page. I originally built a dedicated schedules#happening_now route but I'm not sure the full page is necessary.
Our version of 'happening now' turns into 'upcoming events' if there's no currently active events, so at the end of the day you see what's going on the next morning.
I think it was a big improvement to our event this year over the previous year, especially the front page links.
The text was updated successfully, but these errors were encountered: