Overview:

The Cali personal blog website, available at cali.so, is a source code that requires specific environment variables from other service providers to run correctly. To run this website locally, one would need to configure these environment variables. The .env.example file contains all the necessary environment variables. The technology stack includes Next.js, React, TypeScript, Tailwind CSS, Framer Motion, Radix UI, Clerk, Neon, Drizzle ORM, Sanity, React Email Resend.

Features:

• Next.js: Utilizes Next.js for server-side rendering and generating static websites.
• React: Built with the React library for efficient UI rendering.
• TypeScript: Implements TypeScript for type-checking and improved code quality.
• Tailwind CSS: Uses Tailwind CSS for a utility-first CSS framework.
• Framer Motion: Integrates Framer Motion for animations and transitions.
• Radix UI: Incorporates Radix UI components for building accessible and composable UIs.
• Clerk: Utilizes Clerk for user authentication and management.
• Neon and Drizzle ORM: Implements Neon and Drizzle ORM for managing database operations.
• Sanity: Integrates with Sanity for structured content management.
• React Email Resend: Provides functionality for resending emails using React components.

Installation:

To run the Cali personal blog website locally, follow these steps:

1. Clone the repository:

   git clone [repository-url]
   

2. Install dependencies:

   npm install
   

3. Create a .env file and add the required environment variables as specified in the .env.example file.

4. Start the development server:

   npm run dev
   

5. Access the website on localhost:3000.

Summary:

The Cali personal blog website source code comes with a modern tech stack including Next.js, React, TypeScript, Tailwind CSS, Framer Motion, Radix UI, Clerk, Neon, Drizzle ORM, Sanity, and React Email Resend. Users interested in deploying the website can refer to the official tutorial. Recent updates include migrating to the latest versions of Sanity and Next.js while moving from PlanetScale to Neon database due to changes in database support.