Shadcn Event Calendar Room Bookings

When to use

• Team calendars in month, week, day and agenda views where events are added, edited and dragged
• Room and appointment bookings laid out as one column per resource or as a single day of open slots
• Project and campaign plans drawn as color coded bars spanning several days of a month

When not to use

• Bookings made by dragging across free time, with double booking refused: use the Event Calendar Drag-to-Book example
• Bookings typed into a form that also edits or deletes the one you click: use the Event Calendar Event Form Dialog example
• A finished full page scheduling workspace, such as a hotel desk, shift roster or clinic: use the Event Calendar blocks
• A compact booking card where someone picks a day, then a free time slot, and confirms: use the Schedule blocks
• A plain date or date range input in a form, with no hours, events or dragging: use the Calendar component

Agent notes

• Chip colors are copied from STATUS into each booking's color when built, so changing status later also needs a new color
• addBooking always books noon to 1 PM in room r101 with no overlap check, so repeated clicks double book that hour
• No example passes onEventsChange, so drags, resizes and apiRef edits stay in calendar state and are lost on reload
• New event ids come from a useRef counter that restarts at 0 on every mount, so take ids from your store once events persist

Third-party API docs

• date-fns v4: docs