diff --git a/.env.pullrequest b/.env.pullrequest
new file mode 100644
index 000000000..b3dc083f1
--- /dev/null
+++ b/.env.pullrequest
@@ -0,0 +1,4 @@
+# Point to ix repo PR #2359 with the datetime-input component
+DOCS_BRANCH='docs/date-time-components-guides'
+DOCS_BRANCH_TYPE='pull request'
+DOCS_PR_NUMBER='2359'
diff --git a/docs/components/date-picker/guide.mdx b/docs/components/date-picker/guide.mdx
new file mode 100644
index 000000000..e8d95ce8e
--- /dev/null
+++ b/docs/components/date-picker/guide.mdx
@@ -0,0 +1,68 @@
+---
+doc-type: 'tab-item'
+---
+
+# Date picker - Usage
+
+
+
+1. Month and year navigation
+2. Weekday labels
+3. Week numbers
+4. Selected date or date range
+5. Confirm [button](../button)
+
+## Options
+
+- **Value**: Defines the selected date or date range.
+- **Single selection**: By default, users select date ranges. Use single selection to allow selecting a single date.
+- **Format**: Define the date format that determines how dates are displayed, e.g. `yyyy/LL/dd` for `2024/06/15`.
+- **Week start**: Define which day the week starts on. By default, it will be defined based on the locale.
+- **Week numbers**: Show calendar weeks on the left side of the calendar when needed for reference.
+- **Min and max dates**: Restrict the selectable date range by defining the earliest and latest dates users can choose.
+- **Corners**: By default, date pickers show rounded corners to be consistent with the [dropdown](../dropdown). Use straight, left or right corners to combine with other components.
+
+## Behavior in context
+
+- **Range selection**: In range mode users select a start date and then an end date. The time period between both dates is visually highlighted to provide clear feedback.
+- **Month navigation**: Users can navigate between months using the arrow buttons in the header or the dropdown menu to quickly jump to a specific month and year.
+- **Interaction**: Users can navigate through the date picker using the keyboard. The following keys are supported:
+ - **Tab**: Navigate between areas of the date picker (header, body, footer).
+ - **Arrow keys**: Move through dates in the calendar.
+ - **Enter or click**: Select the highlighted date.
+ - **Escape**: Close date pickers when used in a dropdown. If header dropdown for month/year selection is open, it closes first.
+
+## States
+
+Individual calendar dates within a date picker have five states: Default, hover, active, disabled and focused. Dates outside the allowed range appear in a disabled state and cannot be selected.
+
+
+
+## Dos and Don’ts
+
+
+
+
+- Do use date pickers to ensure accurate date selection
+- Do provide clear labels when the date picker is used in a form context
+- Do ensure the date picker is accessible via keyboard navigation
+- Do use range selection for date periods like booking dates or report timeframes
+- Do set min and max dates to prevent invalid date selections
+
+
+
+
+- Don’t use date pickers for dates that are far in the past or future, use [date inputs](../input) instead
+- Don’t clutter the date picker interface with unnecessary options
+- Don’t forget to handle empty or invalid date states in your validation logic
+
+
+
+
+
+- Do use date time pickers when both date and time information are required
+- Do ensure the date time picker is accessible via keyboard navigation
+- Do use range selection for time periods like booking appointments or scheduling events
+- Do set appropriate min and max dates to prevent invalid selections
+
+
+
+
+- Don’t use date time pickers when only a date or only a time is needed (use [date pickers](../date-picker) or [time pickers](../time-picker) instead)
+- Don’t forget to validate both date and time inputs in your form logic
+- Don’t use date time pickers for dates that are far in the past or future without setting appropriate min and max constraints
+- Don’t clutter the interface with unnecessary time precision when approximate times are sufficient
+
+
+
+
+
+- Do use consistent date and time formats throughout the application to avoid confusion
+- Do provide clear instructions on the expected format, such as "Enter the date time in yyyy/mm/dd HH:mm format"
+- Do consider localization to adapt date and time formats to local conventions
+- Do use separate inputs for start and end date times when defining time ranges
+
+
+
+
+- Don't use date time inputs when only a date or only a time is needed (use [date input](../input-date) or [time input](../input-time) instead)
+
+
+