feat: add shadcn-ui-dashboard

[shadcn-examples]

---

name: "feat: Add new awesome resource"
about: "Propose adding a new awesome resource related to shadcn/ui"
labels:

• feature

---

Describe the awesome resource you want to add

What is it?

Briefly explain what this resource is and why it’s awesome...

Which section does it belong to?

• Libs and Components
• Plugins and Extensions
• Colors and Customizations
• Animations
• Tools
• Websites and Portfolios Inspirations
• Platforms
• Ports
• Design System
• Boilerplates / Templates

Additional details (optional)

Include screenshots, demos, or any other useful context...

Checklist

• I verified that the resource is listed in alphabetical order within its section.
• I checked that the resource is not already listed.
• I provided a clear and concise description of the resource.
• I included a valid and working link to the resource.
• I assigned the correct section to the resource.

Important Notes:

1. If you are introducing a new section, you must also add it to the README.md file and update the table of contents accordingly.
2. This repository focuses on open-source and freely accessible projects. Paid or fully commercial resources will not be accepted.

Just a heads-up: no need to add a date — our system takes care of that automatically!

Also: Don't worry about formatting — our GitHub Action will automatically format the table and make sure everything stays in a single line per entry.

Format your entry like this:

| Name | Description | [Link](Your_Link_Here) |

Thank you for contributing to the awesome-shadcn/ui repository!

Summary by CodeRabbit

• Documentation
  • Added a new “shadcn-ui-dashboard” entry to the Libs and Components list, including description, link, and date.
  • Positioned the new entry after the “shadcn-registry-template” item for easier discovery.
  • No functional or code changes; documentation-only update.

[coderabbitai]

Walkthrough

Documentation update: a new entry for "shadcn-ui-dashboard" was added to the Libs and Components section in README.md, positioned after "shadcn-registry-template". No code or API changes.

Changes

Cohort / File(s)	Summary
Documentation README.md	Added "shadcn-ui-dashboard" entry (name, link, description, date) under Libs and Components, following the "shadcn-registry-template" row.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks (2 passed, 1 warning)

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description is largely the unfilled template: it lacks the required single-line table entry and a working link, and the "What is it?" section remains a placeholder. The checked section ("Boilerplates / Templates") in the PR body conflicts with the actual change in README.md which adds the entry under "Libs and Components," creating a metadata mismatch. The checklist is marked complete but the actual resource line, description, and URL are not present in the PR, so the description does not meet the repository template requirements.	Update the PR description to include the exact markdown table row (for example:

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly and accurately describes the primary change: adding "shadcn-ui-dashboard". It is concise, a single-line summary without extraneous detail or emojis. The README change (adding the new resource entry) matches the title's focus, so the title is appropriate.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

I nibble the docs with whiskers bright,
A dashboard link set just right,
Hop-hop, a row in tidy queue,
Shadcn shines in structured view.
Carrot-checks done, I thump with glee—
Another README victory! 🥕✨

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0333490 and 685de96.

📒 Files selected for processing (1)

• README.md (1 hunks)

🔇 Additional comments (1)

README.md (1)

397-397: Align description casing and confirm OSS vs commercial

• Apply this one-line edit to match README style and use shadcn/ui:

-| shadcn-ui-dashboard | Multipurpose and powerful admin panel template built with Shadcn components. | [Link](https://shadcnuidashboard.com?utm_source=github&utm_content=awesome-shadcn-ui) | 2025-09-12 |
+| shadcn-ui-dashboard | Multipurpose admin dashboard template built with shadcn/ui components. | [Link](https://shadcnuidashboard.com?utm_source=github&utm_content=awesome-shadcn-ui) | 2025-09-12 |

• Verification summary: landing page returns 200 and advertises paid tiers (Hobby $59, Company $129, Enterprise $299); no GitHub repo links or license keywords were found. Because this list targets open-source/free items, either provide a public repository link (preferred) or mark the entry as "Commercial / Paid template".

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}