Odoo — Calendar demo

Calendar & SchedulingSee it livedemo5.odoo.com

A weekly time grid places all-day items above hourly appointments, with a mini calendar and calendar-owner filters in a right rail.

Odoo — Calendar demo — captured interface — Viewport capture · opening screen

Public demo · 2026-09-05Open full image ↗

Calendar & scheduling

Why this pattern works

Team calendars that need both precise scheduling and quick navigation between dates.

Design notes

Surface: Odoo public Demo Company Calendar, week view.
Navigation: Calendar module links above Today, date navigation, view selection, and search.
Layout: Seven-day time grid with an all-day row and a narrow right sidebar.
Density: Moderate, keeping time slots readable and sidebar controls compact.
Color: White and gray grid, pale colored event blocks, small calendar-color markers.
Type: Compact day/date labels and small event text.
Pattern: Separate all-day and timed events while keeping date navigation and calendar visibility close by.
States: Public demo with sample meetings; no event was opened, added, or edited.
Don't: Use more than color to distinguish calendars and preserve readable event text in narrow cells.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Odoo — Calendar demo
Source: https://demo5.odoo.com/odoo/calendar
Swipefile reference: https://swipefile.design/ref/saas-ui-odoo-calendar/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Odoo public Demo Company Calendar, week view.
- nav: Calendar module links above Today, date navigation, view selection, and search.
- layout: Seven-day time grid with an all-day row and a narrow right sidebar.
- density: Moderate, keeping time slots readable and sidebar controls compact.
- color: White and gray grid, pale colored event blocks, small calendar-color markers.
- typography: Compact day/date labels and small event text.
- pattern: Separate all-day and timed events while keeping date navigation and calendar visibility close by.
- states: Public demo with sample meetings; no event was opened, added, or edited.
- dont: Use more than color to distinguish calendars and preserve readable event text in narrow cells.

Useful for: Team calendars that need both precise scheduling and quick navigation between dates.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Team calendars that need both precise scheduling and quick navigation between dates.

Odoo — Calendar demo

Make it your own

Keep exploring