FullCalendar — Weekly schedule

Calendar & SchedulingSee it livefullcalendar.io

A weekly time grid positions timed events against shared hourly rows and a separate all-day band.

FullCalendar — Weekly schedule — captured interface — Viewport capture · opening screen

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

Calendar & scheduling

Why this pattern works

Make time conflicts and available space visible using consistent axes and distinct all-day placement.

Design notes

Surface: Weekly schedule
Navigation: Period arrows, today, and week/day selectors stay above the schedule.
Layout: Seven day columns align against one time axis; overlapping events share horizontal space within a day.
Density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
Color: White grid, fine gray rules, pale current-day tint, and blue event blocks.
Type: Small hour labels and concise event titles support precise reading of compact event blocks.
Pattern: Make time conflicts and available space visible using consistent axes and distinct all-day placement.
States: Public weekly calendar demo with sample all-day and overlapping timed events.
Don't: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

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: FullCalendar — Weekly schedule
Source: https://fullcalendar.io/docs/timegrid-standard-view-demo
Swipefile reference: https://swipefile.design/ref/fullcalendar-week/
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: Weekly schedule
- nav: Period arrows, today, and week/day selectors stay above the schedule.
- layout: Seven day columns align against one time axis; overlapping events share horizontal space within a day.
- density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
- color: White grid, fine gray rules, pale current-day tint, and blue event blocks.
- typography: Small hour labels and concise event titles support precise reading of compact event blocks.
- pattern: Make time conflicts and available space visible using consistent axes and distinct all-day placement.
- states: Public weekly calendar demo with sample all-day and overlapping timed events.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Make time conflicts and available space visible using consistent axes and distinct all-day placement.

## 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: Make time conflicts and available space visible using consistent axes and distinct all-day placement.

FullCalendar — Weekly schedule

Make it your own

Keep exploring