Update README.md

[piths]

includeus s--testingssvsvsv sv s

---

Summary by cubic

Renamed the README title to “Devorc Dashboard” and removed the outdated header image to match current branding.

Summary by CodeRabbit

• Documentation
  • Renamed the primary README heading to “Devorc Dashboard” to reflect current branding.
  • Removed the outdated hero image from the top of the README to simplify the page and avoid confusion.
  • All other README content remains unchanged; no functionality or public interfaces were affected.
  • Improves clarity for new users and aligns the landing documentation with the latest product identity.

[coderabbitai]

Walkthrough

The README was updated: the main heading was renamed from “Orcish Dashboard” to “Devorc Dashboard,” and the top hero image line was removed. No other content or code was modified.

Changes

Cohort / File(s)	Summary
Docs refresh README.md	Renamed top-level heading to “Devorc Dashboard”; removed the hero image line; retained all other README content unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled titles, neat and small,
Swapped “Orcish” for “Devorc” on the wall.
The banner hopped away—no pic to see—
But carrots of clarity remain for thee.
Thump-thump! A README trimmed with cheer,
Fresh as clover, tidy here.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title "Update README.md" correctly indicates which file was changed but is too generic to summarize the primary change; the PR actually renames the README heading from "Orcish Dashboard" to "Devorc Dashboard" and removes the hero image line. Because the title does not communicate those specific edits or the intent behind them, it does not meet the guideline of highlighting the most important change. Under the provided criteria this makes the title inconclusive.	Please replace the generic title with a concise, descriptive one such as "Rename README heading to 'Devorc Dashboard' and remove hero image" or "Update README: rename heading and remove hero image" so reviewers can quickly grasp the primary change; update the PR title before merging.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

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

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.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (4)

README.md (4)

1-1: Heading rename introduces brand inconsistency with repo and body text

Repo is "orcish-dashboard" and Line 6 still says "The Orcish Dashboard". If the rename to "Devorc" was accidental, revert the H1. If the rename is intentional, update the rest of the README accordingly.

Revert option:

-# Devorc Dashboard
+# Orcish Dashboard

Intentional rename option (minimal consistency fix shown; adjust elsewhere as needed):

-## Overview
-The Orcish Dashboard is a sleek and modern dashboard built with Shadcn. It features a responsive design with support for both light and dark modes, along with a customizable theme selector that lets you easily switch between different color schemes.
+## Overview
+The Devorc Dashboard is a sleek and modern dashboard built with shadcn/ui. It features a responsive design with support for both light and dark modes, along with a customizable theme selector that lets you easily switch between different color schemes.

---

18-18: Fix Markdown heading hierarchy

There should be a single H1 per doc. Demote “Development Server” to align with “Overview”/“Getting Started”.

-# Development Server
+## Development Server

---

12-16: Be explicit and consistent about package manager

You install with pnpm but show multiple runners below. Either keep one flow or add a note to use the same manager for install and dev.

Option A (pnpm-focused):

-```bash
-pnpm i
-```
+```bash
+pnpm install
+```
@@
-```bash
-npm run dev
-# or
-yarn dev
-# or
-pnpm dev
-# or
-bun dev
-```
+```bash
+pnpm dev
+```

Option B (keep all, add guidance):

 To begin, install the required dependencies using the following command:
 
 ```bash
 pnpm i

@@
-After installing the dependencies run the development server:
+After installing the dependencies, run the development server (use the same package manager you used to install):

Also applies to: 22-30

---

`6-6`: **Product/library naming**

Capitalize/reference the library as “shadcn/ui” and consider linking to its docs for clarity.


```diff
-The Orcish Dashboard is a sleek and modern dashboard built with Shadcn.
+The Orcish Dashboard is a sleek and modern dashboard built with shadcn/ui.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 226e7ca and 6244106.

📒 Files selected for processing (1)

• README.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: cubic · AI code reviewer

[cubic-dev-ai]

No issues found across 1 file