Chore: Add registry file for Atomic CRM

Author: jonathanarnault

.gitignore

@@ -33,4 +33,7 @@ dist/
 /lib/
 .env
 *storybook.log
-.claude
+.claude
+
+# Shadcn Registry
+public/r/

demo/App.tsx

@@ -1,5 +1,8 @@
-import { CRM } from "@/atomic-crm/root/CRM";
-import { authProvider, dataProvider } from "@/atomic-crm/providers/fakerest";
+import { CRM } from "@/components/atomic-crm/root/CRM";
+import {
+  authProvider,
+  dataProvider,
+} from "@/components/atomic-crm/providers/fakerest";
 
 const App = () => (
   <CRM dataProvider={dataProvider} authProvider={authProvider} />

doc/src/content/docs/developers/customizing.mdx

@@ -10,7 +10,7 @@ Developers can customize the Atomic CRM application to suit their business needs
 The entry point of the frontend application is the `src/App.tsx` file. By default, this file simply renders the `<CRM>` component, which is the root component of Atomic CRM.
 
 ```tsx
-import { CRM } from "@/atomic-crm/root/CRM";
+import { CRM } from "@/components/atomic-crm/root/CRM";
 
 const App = () => <CRM />;
 
@@ -22,7 +22,7 @@ export default App;
 For instance, the following code snippet shows how to customize the CRM application domain-specific data.
 
 ```tsx
-import { CRM } from "@/atomic-crm/root/CRM";
+import { CRM } from "@/components/atomic-crm/root/CRM";
 
 const App = () => (
     <CRM
@@ -80,7 +80,7 @@ The only data sent to the telemetry server is the admin domain (e.g. “example.
 You can opt out of telemetry by simply adding `disableTelemetry` to the `<CRM>` component:
 
 ```tsx
-import { CRM } from "@/atomic-crm/root/CRM";
+import { CRM } from "@/components/atomic-crm/root/CRM";
 
 const App = () => <CRM disableTelemetry />;
 

doc/src/content/docs/developers/data-providers.mdx

@@ -39,8 +39,8 @@ If you want to set up the FakeRest data provider manually, you need to change th
 
 ```diff
 // in App.tsx
-import { CRM } from "@/atomic-crm/root/CRM";
-+import { authProvider, dataProvider } from "@/atomic-crm/providers/fakerest";
+import { CRM } from "@/components/atomic-crm/root/CRM";
++import { authProvider, dataProvider } from "@/components/atomic-crm/providers/fakerest";
 
 const App = () => (
 -    <CRM />

doc/src/content/docs/index.mdx

@@ -87,7 +87,7 @@ If you need to reset the database, stop the Supabase instance with `npx supabase
 The entry point of the application is the `src/App.tsx` file. By default, this file simply renders the `<CRM>` component, which is the root component of Atomic CRM.
 
 ```tsx
-import { CRM } from "@/atomic-crm/root/CRM";
+import { CRM } from "@/components/atomic-crm/root/CRM";
 
 const App = () => <CRM />;
 
@@ -97,7 +97,7 @@ export default App;
 `<CRM>` accepts various props to customize the application domain and look and feel. For instance, the following code snippet shows how to customize the app title, the task types, and deal categories.
 
 ```tsx {5-7}
-import { CRM } from "@/atomic-crm/root/CRM";
+import { CRM } from "@/components/atomic-crm/root/CRM";
 
 const App = () => (
     <CRM

makefile

@@ -85,3 +85,6 @@ doc-preview: doc-build
 
 doc-deploy:
 	@(cd doc && npx gh-pages -d dist -e doc -b gh-pages -m "Deploy docs" --remove doc)
+
+registry-build: ## build the shadcn registry
+	npm run registry:build