Dokploy / Dokploy/dokploy

Standardize Empty/Skeleton states across Dokploy UI for consistency, accessibility, and reduced layout shift

Open
#3,513 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

The UI currently shows inconsistent loading and empty states (plain text, different layouts, mixed affordances). This causes visual jitter, unclear guidance, and uneven UX across dashboards and dialogs. It also makes the UI harder to scan and less accessible for keyboard and screen-reader users.

Describe the solution you'd like

Adopt a single Empty/Skeleton pattern (shadcn Empty + Skeleton) across all dashboards, dialogs, tables, and selectors. Replace text-only “Loading…” and “No results” blocks with consistent Empty layouts and use EmptyContent for CTAs. Add a reusable ListSkeleton helper to standardize list loading layouts. Ensure key flows (projects, servers, requests, monitoring, deployments, schedules, backups, providers, domains, settings) use the same approach.

Additional context

No response

Will you send a PR to implement it?

Yes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inventorying the dashboards, dialogs, tables, and selectors named in the issue, then inspect the current Empty and Skeleton usage. The work is done when the listed flows use consistent Empty layouts, EmptyContent CTAs, and ListSkeleton loading states without text-only loading or empty blocks.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
accessibility, design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.