The discussion centers on improving Oneboxes for events to include critical metadata such as date, time, and description, rather than relying on the workaround of embedding this information in topic titles. nathank initiated the thread by highlighting the current limitations of event Oneboxes and suggesting that they should mirror the rich card interface found in the calendar. opcourdis supported the idea, noting it would enhance event promotion.
sam proposed a fundamental architectural change: introducing dedicated event URLs (e.g., /event/slug) to enable proper Oneboxing. This approach would require determining how users access these links, with chapoi agreeing that adding them to the context menu is the appropriate solution. nathank followed up to check on progress, reiterating the necessity of displaying event details directly in the Onebox.
The thread concludes with nathank celebrating the successful implementation of this feature, sharing a link to a newly formatted event Onebox as proof of the improvement. The feature has been marked as completed, resolving the initial request for better visual representation of event data in topic previews.
At present, the Oneboxes for events are a bit meh. Basically, they are no different to regular topic Oneboxes, and don’t include the date, time, description, etc etc (unless put into the Topic Title as a workaround).
Here is an example event from our site:
Would it be possible to hook into the new (and brilliant) cards that appear on click in the calendar for events, and serve these up as oneboxes? For example:
That might not be feasible at all, but I do wonder if the metadata could be modified for event posts so that they Onebox in a way that highlights the critical event info (especially internally).
I’ve just oneboxed a couple of events today, and found I had to add the date / time into the title so they made sense. That really shouldn’t be necessary.