> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/availability/creating-a-calendar/creating-a-calendar-1.md).
# Creating Day Types
## **Creating day types**
The next page is about creating the different types of days that you want. These typically correspond to what you've used in the past (peak, non-peak, holiday, etc.)
To create a custom day, click on **+ Add custom day type**. It'll bring up the selection below. To start with, add a name for your day type. Then pick a color.
Next, simply click on the dates in the calendar on the right hand side to specify these days as that day type. In the image below, we've specified the 8th, 14th, 20th, 26th, and 29th November as Peak Days.
You can use the arrows on either side of the month/year to move across the season and create this day type for each month. Once you're done, hit **Save**.
Rinse and Repeat for additional day types. You should end up with something like this:
Once you've added in all of your day types, click **Next**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/availability/creating-a-calendar/creating-a-calendar-1.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
