You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Curious about the engineering decisions behind Neotion? Check out [`learn.md`](./learn.md) for an in-depth look at:
58
+
59
+
-**Why we chose Convex** over traditional databases for real-time collaboration
60
+
-**How we solved real-time editor synchronization** with TipTap and atomic operations
61
+
-**The security architecture** that ensures user data isolation
62
+
-**Key lessons learned** from building a collaborative platform
63
+
64
+
Perfect for developers who want to understand the technical challenges and architectural decisions that make Neotion work.
65
+
55
66
---
56
67
57
-
## ✨ Core Features
68
+
## ✨ Features
58
69
59
70
This section highlights the key workflows that deliver the most value to our users. Understanding these features will get you up and running with Neotion's core functionality quickly.
60
71
@@ -160,6 +171,8 @@ The project follows a standard Next.js App Router structure, with clear separati
160
171
161
172
## 🔧 Installation
162
173
174
+
### Method 1: Local Development Setup
175
+
163
176
1.**Clone the repository:**
164
177
165
178
```bash
@@ -174,13 +187,41 @@ The project follows a standard Next.js App Router structure, with clear separati
174
187
```
175
188
176
189
3. **Set up environment variables:**
177
-
Create a `.env.local` file in the root of the project and add the variables from the table below.
190
+
Create a `.env.local` file in the root of the project and add the variables from the [Environment Variables](#️-environment-variables) table below.
Open your browser and navigate to `http://localhost:3000`
220
+
221
+
**Note:** Replace the placeholder values with your actual environment variables. For easier management, you can create a `.env` file and use `--env-file .env` instead of individual `-e` flags.
0 commit comments