Add Atomic CRM to boilerplates/templates list

[fzaninotto]

---

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?

Atomic CRM is an open-source CRM built with shadcn ui and supabase.

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

Not sure about the others

Additional details (optional)

Demo: https://marmelab.com/atomic-crm-demo/

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 Atomic CRM to the Libs & Components table with name, brief description, demo link, repository link, and date.
  • Added Atomic CRM to the Boilerplates / Templates table with the same details for consistency.
  • No removals or edits to existing entries; changes are limited to README documentation only.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Added two new rows for "Atomic CRM" to README.md: one under "Libs and Components" and one under "Boilerplates / Templates," each with description, demo URL, GitHub link, and date (2025-09-16). No other files or code were changed.

Changes

Cohort / File(s)	Summary of changes
Docs — README update README.md	Appended two Markdown table rows for "Atomic CRM": one in "Libs and Components" and one in "Boilerplates / Templates". Each row includes name, description (React CRM on Supabase with demo URL), GitHub link, and date 2025-09-16. No deletions or other modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit peeks at docs tonight,
Two new rows placed just right.
Links aglow and dates aligned,
No code touched, the branches signed.
Hop, commit, let readers find. 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description follows the repository template (front matter, "What is it?", chosen section, demo link, and completed checklist) and provides a concise resource description, but it does not reflect all file-level changes: the README diff shows two new entries (one in "Libs and Components" and one in "Boilerplates / Templates") while the description only states adding to "Boilerplates / Templates", creating a mismatch that should be resolved before merge.	Please update the PR description to accurately list and justify the actual README changes: either remove the unintended "Libs and Components" entry or explain why Atomic CRM belongs in both sections, include (or reference) the exact table row(s) you added, confirm the date was not manually inserted if the repo automates it, and re-verify alphabetical ordering and link validity so reviewers can validate the change quickly.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title is a short, single sentence that clearly states the primary change — adding "Atomic CRM" to the boilerplates/templates list — and is directly relevant to the README modifications described in the PR. It is concise, specific, and easy for a teammate scanning history to understand the main intent of the change.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

📜 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 d3ac1e2 and 01598a5.

📒 Files selected for processing (1)

• README.md (1 hunks)

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: 1

📜 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 50e06da.

📒 Files selected for processing (1)

• README.md (1 hunks)

🔇 Additional comments (1)

README.md (1)

368-368: Alphabetical placement and date format look good.

Entry is correctly placed under “A” and uses ISO date (2025-09-16).

[coderabbitai]

⚠️ Potential issue

Fix broken repo/demo links; clarify shadcn/ui in description.

• The GitHub link should point to marmelab/atomic-crm (current org link 404s). (github.com)
• The demo URL appears to be https://marmelab.com/atomic-crm/ (not …/atomic-crm-demo). (github.com)
• Consider explicitly mentioning shadcn/ui to align with the list’s scope.

Apply this diff:

-| Atomic CRM | Open-source React CRM built on top of Supabase [Demo site](https://marmelab.com/atomic-crm-demo) | [Link](https://github.com/atomic-crm) | 2025-09-16 |
+| Atomic CRM | Open-source React CRM built with shadcn/ui and Supabase. [Demo site](https://marmelab.com/atomic-crm/) | [Link](https://github.com/marmelab/atomic-crm) | 2025-09-16 |

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In README.md around line 368, the row for "Atomic CRM" has incorrect links and
an incomplete description; update the GitHub link to
https://github.com/marmelab/atomic-crm, change the demo URL to
https://marmelab.com/atomic-crm/ (remove "-demo"), and adjust the description
text to explicitly mention shadcn/ui (e.g., "Open-source React CRM built on top
of Supabase, using shadcn/ui") so the table entry points to the correct
repo/demo and includes the shadcn/ui note.