Problem
Astryx ships Calendar, DateInput, DateRangeInput, and TimeInput, but none of the 43 page templates actually renders a calendar. The only occurrences of "Calendar" under templates/pages/ are CalendarIcon in detail-page and a docs listing in documentation. DateInput, DateRangeInput, and TimeInput do not appear in any page template at all.
That leaves a gap for date-driven screens. An agent asked to build a booking page, an interview scheduler, or a shift planner has no page-level example to start from, so it wraps the calendar in hand-rolled markup instead of a proven frame.
Evidence of demand
Date-driven pages are a standard archetype across product categories: booking and reservations, interview scheduling, shift and resource planning, appointment management, content calendars. MUI and Ant Design both ship calendar components, and products built on them converge on the same two-part frame — a calendar that drives a detail list for the selected day.
The pattern is also close to frames you already have. incident-console and messaging-shell are both frame-first archetypes where one pane drives another. A scheduling page is that same idea with a date as the selector.
Why existing templates don't cover it
table-page and library handle browsing, but neither has a date as the primary axis. form-two-column and contact-form collect a date inside a form rather than using it as a navigational surface. No current template changes what the page shows when a date is selected.
Proposed template
scheduling — a calendar-first frame where date selection drives a detail panel.
Layout and SideNav frame, with DateRangeInput and Selector filters in the navCalendar as the primary surface in the content area, holding selected-day stateLayoutPanel on the right listing entries for the selected day, each an Item with Avatar, Text, Timestamp, and StatusDotEmptyState when the selected day has no entriesDialog for creating an entry, built from DateInput, TimeInput, Field, and TextInput
Out of scope
No new components. No week or month view toggle in v1. No drag to reschedule. No recurrence rules.
Doc entry
{
type: 'page',
name: 'Scheduling',
displayName: 'Scheduling',
description: 'Calendar-driven scheduling page with a day detail panel',
isReady: true,
category: 'Scheduling - Calendar',
}Notes
Happy to reshape the composition before I start. I would follow the template grading rubric: layout primitives only, no inline styles, tokens throughout. CLA is signed.
Problem
Astryx ships
Calendar,DateInput,DateRangeInput, andTimeInput, but none of the 43 page templates actually renders a calendar. The only occurrences of "Calendar" undertemplates/pages/areCalendarIconindetail-pageand a docs listing indocumentation.DateInput,DateRangeInput, andTimeInputdo not appear in any page template at all.That leaves a gap for date-driven screens. An agent asked to build a booking page, an interview scheduler, or a shift planner has no page-level example to start from, so it wraps the calendar in hand-rolled markup instead of a proven frame.
Evidence of demand
Date-driven pages are a standard archetype across product categories: booking and reservations, interview scheduling, shift and resource planning, appointment management, content calendars. MUI and Ant Design both ship calendar components, and products built on them converge on the same two-part frame — a calendar that drives a detail list for the selected day.
The pattern is also close to frames you already have.
incident-consoleandmessaging-shellare both frame-first archetypes where one pane drives another. A scheduling page is that same idea with a date as the selector.Why existing templates don't cover it
table-pageandlibraryhandle browsing, but neither has a date as the primary axis.form-two-columnandcontact-formcollect a date inside a form rather than using it as a navigational surface. No current template changes what the page shows when a date is selected.Proposed template
scheduling— a calendar-first frame where date selection drives a detail panel.LayoutandSideNavframe, withDateRangeInputandSelectorfilters in the navCalendaras the primary surface in the content area, holding selected-day stateLayoutPanelon the right listing entries for the selected day, each anItemwithAvatar,Text,Timestamp, andStatusDotEmptyStatewhen the selected day has no entriesDialogfor creating an entry, built fromDateInput,TimeInput,Field, andTextInputOut of scope
No new components. No week or month view toggle in v1. No drag to reschedule. No recurrence rules.
Doc entry
Notes
Happy to reshape the composition before I start. I would follow the template grading rubric: layout primitives only, no inline styles, tokens throughout. CLA is signed.