A calendar places events against time itself: the position of a block says when it happens, and its size says how long it lasts. Orvain's Calendar family ships three views of one component, a day behind a thirteen-hour axis with a line that tracks the current time, a week of seven day-of-week columns where overlapping events stack in a ranked order, and a month grid with out-of-month days hatched, today badged, and event chips that truncate to fit their cell. Five headers sit on top of any of them: one with notifications and an overflow menu, one with a filter, one with search and a month picker, one with a tear-off today tile and quick add, and one with a scrolling strip of days.
Overlap is the problem the whole component is arranged around. Two events at ten o'clock have to share a column without either one disappearing, and once five of them start at ten the view must choose between shrinking every card past reading and hiding some behind a count. A month cell cannot express duration at all, which makes the month view a density map rather than a schedule: it answers which days are busy, and anyone hunting for a clash has to be sent to the week or the day.
Appointments down an hour axis, with the current-time line telling the front desk how far behind the morning has slipped. The day view is the only one where a fifteen-minute gap is visible as a gap.
A week of shifts, a column per day, so the hole on Thursday afternoon is obvious before anyone adds up hours. Overlapping shifts stack in order instead of hiding one another.
Scheduled posts across a month, where the question is whether next week is overloaded rather than what time anything goes out. Chips truncate, because the title is a label here, not the content.
Bookable space shown as the hours already taken. Whoever is booking reads the empty space, so free time has to be as legible as busy time, not just the absence of a card.
A date picker is an input. It exists to return a date to a form and closes as soon as it has one. A calendar is a view: it shows what already occupies the time, stays open while you work, and usually supports creating and moving events. They share a month grid, which is why they get confused, but only one of them carries a value.
In day and week views, split the column into side-by-side lanes and keep the earliest event leftmost, so the layout stays stable as events are added. Cap the lanes and collapse the remainder behind a count, since four cards in one hour are already too narrow to read. In a month cell, show the chips that fit and put the rest behind a link that opens the day.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
A calendar places events against time itself: the position of a block says when it happens, and its size says how long it lasts. Orvain's Calendar family ships three views of one component, a day behind a thirteen-hour axis with a line that tracks the current time, a week of seven day-of-week columns where overlapping events stack in a ranked order, and a month grid with out-of-month days hatched, today badged, and event chips that truncate to fit their cell. Five headers sit on top of any of them: one with notifications and an overflow menu, one with a filter, one with search and a month picker, one with a tear-off today tile and quick add, and one with a scrolling strip of days.
Overlap is the problem the whole component is arranged around. Two events at ten o'clock have to share a column without either one disappearing, and once five of them start at ten the view must choose between shrinking every card past reading and hiding some behind a count. A month cell cannot express duration at all, which makes the month view a density map rather than a schedule: it answers which days are busy, and anyone hunting for a clash has to be sent to the week or the day.
Appointments down an hour axis, with the current-time line telling the front desk how far behind the morning has slipped. The day view is the only one where a fifteen-minute gap is visible as a gap.
A week of shifts, a column per day, so the hole on Thursday afternoon is obvious before anyone adds up hours. Overlapping shifts stack in order instead of hiding one another.
Scheduled posts across a month, where the question is whether next week is overloaded rather than what time anything goes out. Chips truncate, because the title is a label here, not the content.
Bookable space shown as the hours already taken. Whoever is booking reads the empty space, so free time has to be as legible as busy time, not just the absence of a card.
A date picker is an input. It exists to return a date to a form and closes as soon as it has one. A calendar is a view: it shows what already occupies the time, stays open while you work, and usually supports creating and moving events. They share a month grid, which is why they get confused, but only one of them carries a value.
In day and week views, split the column into side-by-side lanes and keep the earliest event leftmost, so the layout stays stable as events are added. Cap the lanes and collapse the remainder behind a count, since four cards in one hour are already too narrow to read. In a month cell, show the chips that fit and put the rest behind a link that opens the day.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.