Calendar Component: Add Description and Image Fields to All Views (Especially Agenda)

[nocodeandy]

Extend the Calendar component to support Description and Image fields alongside Title and Dates, bringing it in line with the standard collection component field set.

---

Summary

The Calendar component currently exposes only Title and Date fields for data binding, leaving builders without the ability to surface contextual information — like a description or visual — directly in calendar and agenda views. Most other collection components (e.g., List, Cards, Table) support at minimum a Title, Description, and Image. Calendar should meet this baseline to be useful for real-world scheduling and event-display use cases.

Current Problem

Calendar is limited to Title and Date (start/end) field bindings. There is no way to attach a Description or Image to calendar entries within the component itself. Builders who want to surface event details are forced to rely on users tapping through to a detail screen, which adds friction and limits the utility of the calendar as a glanceable, information-dense view — particularly in Agenda mode where vertical space is available and additional context would be natural.

Examples/Scenarios

• A builder creating an employee events calendar wants each agenda entry to show the event title, a short description (e.g., "All-hands meeting — Building 3, Floor 2"), and a thumbnail image or avatar. Currently, only the title is visible in the agenda row.
• A project timeline app uses Calendar to display deliverables. Builders want a description field ("Owner: Marketing / Status: In Review") visible inline without requiring a tap.
• A booking or scheduling app wants to display a service image or staff avatar alongside appointment entries in Agenda view for faster visual scanning.

Why This Matters

• Consistency across collections: Title + Description + Image is the expected baseline for any collection-type component in Glide. Calendar being the exception creates an inconsistent builder experience.
• Agenda view is underutilized: The agenda layout has natural vertical space that currently goes unused. Supporting additional fields would make it meaningfully more useful for information-dense scheduling UIs.
• Reduces tap depth: Surfacing key details inline reduces the need to navigate to a detail screen for routine information, improving end-user efficiency.
• Enterprise and ops use cases: Teams using Calendar for scheduling, resource management, or project tracking need more than a title to make the view actionable at a glance.

Suggested UX

• Description Field

  • Add an optional Description binding in the Calendar component panel, similar to how List and Cards handle subtitles.
  • Render below the Title in both Agenda and (where space permits) Month/Week views.
  • Support truncation with ellipsis for compact views; full display in Agenda rows.

• Image Field

  • Add an optional Image binding rendered as a small thumbnail or avatar (similar to List component image treatment).
  • In Agenda view: left-aligned thumbnail beside the title/description block.
  • In Month/Week views: optionally show as a small icon or avatar if space allows, hidden by default to preserve density.

• Defaults and Backwards Compatibility

  • Both fields should be optional — existing Calendar configurations remain unaffected.
  • Smart defaults: if no image is bound, no placeholder space is reserved.

Bringing Calendar up to the standard collection field baseline (Title, Description, Image) would meaningfully expand its utility, especially for the Agenda view, without adding complexity for builders who don't need the additional fields.