> For the complete documentation index, see [llms.txt](https://docs.labii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labii.com/widgets/section-widgets/productivity/calendars.md). # Calendars ## Overview Calendar-type widgets are versatile tools integrated with a comprehensive calendar interface, offering users a diverse range of functionalities to manage and organize events, tasks, and deadlines effectively. These widgets are designed to provide a user-friendly experience by displaying dates, events, and schedules across various views such as month, week, and agenda, facilitating seamless navigation and planning. Users can easily add, edit, and delete events directly within the widget, ensuring efficient scheduling and coordination. With customizable settings and interactive features, calendar-type widgets serve as centralized hubs for optimizing time management, promoting collaboration, and enhancing productivity within diverse workflows and projects. ## Widgets * [Calendar](/widgets/section-widgets/productivity/calendars/calendar.md) - Efficiently create and manage events * [Scheduling](/widgets/section-widgets/productivity/calendars/scheduling.md) - Schedule equipment that makes utilization attributable to the person using the equipment --- # 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://docs.labii.com/widgets/section-widgets/productivity/calendars.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.