cleanup readme

Author: izadoesdev

README.md

@@ -20,7 +20,6 @@
 [![GitHub Stars](https://img.shields.io/github/stars/databuddy-analytics/Databuddy?style=social)](https://github.com/databuddy-analytics/Databuddy/stargazers)
 [![Twitter](https://img.shields.io/twitter/follow/trydatabuddy?style=social)](https://twitter.com/trydatabuddy)
 
-
 </div>
 
 A comprehensive analytics and data management platform built with Next.js, TypeScript, and modern web technologies. Databuddy provides real-time analytics, user tracking, and data visualization capabilities for web applications.
@@ -38,7 +37,7 @@ A comprehensive analytics and data management platform built with Next.js, TypeS
 - 🎯 Goal tracking
 - 📈 Conversion analytics
 - 🔍 Custom event tracking
-- 📊 Funnel analysis 
+- 📊 Funnel analysis
 - 📈 Cohort analysis // Soon
 - 🔄 A/B testing // Soon
 - 📈 Export capabilities // Soon
@@ -48,7 +47,6 @@ A comprehensive analytics and data management platform built with Next.js, TypeS
 
 ## 📚 Table of Contents
 
-- [Project Structure](#project-structure)
 - [Getting Started](#getting-started)
 - [Development](#development)
 - [Contributing](#contributing)
@@ -70,25 +68,26 @@ A comprehensive analytics and data management platform built with Next.js, TypeS
 ### Installation
 
 1. Clone the repository:
+
 ```bash
 git clone https://github.com/databuddy/databuddy.git
 cd databuddy
 ```
 
-2. Install dependencies (Bun only):
+2. Install dependencies:
+
 ```bash
 bun install
 ```
 
 3. Set up environment variables:
+
 ```bash
-cp apps/dashboard/.env.example apps/dashboard/.env
-cp apps/landing/.env.example apps/landing/.env
-cp apps/admin/.env.example apps/admin/.env
-cp apps/api/.env.example apps/api/.env
+cp .env.example .env
 ```
 
-4. Start development servers (Bun only):
+4. Start development servers:
+
 ```bash
 bun run dev
 ```
@@ -99,12 +98,16 @@ bun run dev
 
 Check the root `package.json` for available scripts. Here are some common ones:
 
-- `bun run dev` - Start all applications in development mode (if defined)
+- `bun run dev` - Start all applications in development mode
+- `bun run build` - Build all applications
+- `bun run start` - Start all applications in production mode
+- `bun run lint` - Lint all code with Ultracite
+- `bun run format` - Format all code with Prettier
+- `bun run check-types` - Type check all TypeScript code
 - `bun run db:studio` - Open Drizzle Studio for database management
-- `bun run clickhouse:init` - Initialize ClickHouse tables
 - `bun run db:generate` - Generate Drizzle ORM types
-- `bun run db:push` - Apply database migrations
-- `bun run db:migrate` - Generate and run migrations
+- `bun run db:push` - Apply database schema changes
+- `bun run db:migrate` - Run database migrations
 - `bun run db:deploy` - Deploy database migrations
 - `bun run sdk:build` - Build the SDK package
 - `bun run email:dev` - Start the email development server
@@ -114,29 +117,34 @@ You can also `cd` into any package and run its scripts directly.
 ### Development Workflow
 
 1. Create a new branch:
+
 ```bash
 git checkout -b feature/your-feature
 ```
 
 2. Make your changes
 
 3. Run tests:
+
 ```bash
 bun run test
 ```
 
 4. Create a changeset:
+
 ```bash
 bun run changeset
 ```
 
 5. Commit your changes:
+
 ```bash
 git add .
 git commit -m "feat: your feature"
 ```
 
 6. Push your changes:
+
 ```bash
 git push origin feature/your-feature
 ```
@@ -170,7 +178,7 @@ See [SECURITY.md](SECURITY.md) for reporting vulnerabilities.
    See [Prerequisites](#prerequisites).
 
 2. **How do I deploy?**
-   See [Deployment](#deployment).
+   See the deployment documentation in our [docs](https://docs.databuddy.cc).
 
 3. **How do I contribute?**
    See [Contributing](#contributing).
@@ -207,5 +215,7 @@ See [ACKNOWLEDGMENTS.md](ACKNOWLEDGMENTS.md) for credits.
 - **Always use error boundaries properly.**
 - **Console usage:** Use `console.error`, `console.time`, `console.json`, `console.table`, etc. appropriately.
 - **Almost never use useEffect** unless critical.
+- **Use Ultracite** for linting and formatting.
+- **Use Prettier** for code formatting.
 
 See `.cursor/rules/` for the full enforced ruleset.