> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Calendar

> Sub-primitive used within DateTimePicker. It can be used independently or with a Clock depending on whether the user needs a date, a time, or both.

## Calendar

<Badge color="blue">v1.0.0</Badge> | *Storybook link coming soon*

### When to use

* Date only: scheduling, deadlines, date of birth, any input where formatted date is irrelevant.
* Date and time together: event scheduling, log entries, anything time-sensitive where both formatted date and time matter.

### Dos and don'ts

* Do set min and max constraints when the valid range is known — don't make users discover invalid dates by trial and error.
* Do pre-populate with a sensible default when one exists; an empty date field with no anchor is harder to interact with.
* Do be explicit about timezone when it matters — don't silently assume local time if users are in different regions.
* Don't combine date and time if only one is needed — the extra input adds friction without value.
* Don't use freeform text input as a fallback for mobile — use the native picker or a well-constrained input pattern.

### Often used with

* [Clock](/aura-design-system/primitives/clock) when both date and time are required and [DateTimePicker](/aura-design-system/primitives/date-and-time-picker).