Tabler — Task list

Project ManagementSee it livepreview.tabler.io

A grouped task list exposes owner, due date, and priority in consistent columns.

Tabler — Task list — captured interface — Viewport capture · opening screen

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

Navigation

Why this pattern works

Offer a compact alternative to a board when users need to compare many tasks and deadlines.

Design notes

Surface: Task list
Navigation: The app header stays global; a new-task action belongs to each status section.
Layout: Status sections each contain a compact table with checkboxes and row actions.
Density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
Color: White rows on a pale background with small colored priority labels.
Type: Short headings and aligned metadata create a steady scanning rhythm across rows.
Pattern: Offer a compact alternative to a board when users need to compare many tasks and deadlines.
States: Populated demo tasks grouped by progress stage.
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: Tabler — Task list
Source: https://preview.tabler.io/tasks-list.html
Swipefile reference: https://swipefile.design/ref/tabler-task-list/
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: Task list
- nav: The app header stays global; a new-task action belongs to each status section.
- layout: Status sections each contain a compact table with checkboxes and row actions.
- density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
- color: White rows on a pale background with small colored priority labels.
- typography: Short headings and aligned metadata create a steady scanning rhythm across rows.
- pattern: Offer a compact alternative to a board when users need to compare many tasks and deadlines.
- states: Populated demo tasks grouped by progress stage.
- 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: Offer a compact alternative to a board when users need to compare many tasks and deadlines.

## 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: Offer a compact alternative to a board when users need to compare many tasks and deadlines.

Tabler — Task list

Make it your own

Keep exploring