# 📅 Event Location/Description

**URL:** https://meta.discourse.org/t/event-location-description/371606
**Category:** Announcements
**Tags:** events
**Created:** [June 25, 2025, 8:31am UTC](https://meta.discourse.org/t/event-location-description/371606 "2025-06-25T08:31:12Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![nathank](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nathank/32/290039_2.png) [@nathank](https://meta.discourse.org/u/nathank)
#### Post date: [June 27, 2025, 7:31pm UTC](https://meta.discourse.org/t/event-location-description/371606/2 "2025-06-27T19:31:46Z")

</div>

This is brilliant, and a much more flexible and high value use of the existing fields - it is also consistent with how most email calendars handle their events.

Would now be a good time to remove the `Minimal Event` option?

> [@What is the point of the 'Minimal Event' setting in the Add event modal? And why is it separate?](https://meta.discourse.org/t/what-is-the-point-of-the-minimal-event-setting-in-the-add-event-modal-and-why-is-it-separate/359956):
>
> I’m referring to this: I struggle to see how this would be helpful, but I’m sure it has some history. A Standalone event almost certainly does what is needed though, and I believe that this is completely redundant. My users often tick it without realising what it does, and I had to go in and undo that quite a bit. Therefore, now I hide it in my instances with this CSS: // hides minimal event option .event-field.minimal-event { display: none; } Pe…

---

_[View the full topic](https://meta.discourse.org/t/event-location-description/371606)._
