Shared Diary Collaborative Platform
Private Collaborative Journal Platform with Administrative Approval Workflows, Emotion Tagging, and Date-Grouped Reflection Timelines

System Context & Value Proposition
Shared Diary is a dedicated collaborative web application designed for trusted peer groups and close friend circles to record reflections and memories in a safe, distraction-free environment. Departing from toxic social media mechanics, the application emphasizes psychological safety through private group access tokens, administrator approval controls, and chronological day-by-day journal feeds.
Modern social platforms prioritize public engagement algorithms, advertisements, and vanity metrics, leaving small communities without a secure, intimate digital space for personal storytelling.
System Architecture & Execution Flow
React + TypeScript Client (Vercel)
↓
Firebase Authentication (Session Token)
↓
Admin Approval Guard (Pending vs Approved Verification)
↓
Cloud Firestore Database
↓
Date-Grouped Diary Collections & Private Circle FeedsMulti-Tier Architectural Layers
React, TypeScript, Tailwind CSS
Type-safe component architecture with clean distraction-free typography, optimistic UI updates, and responsive mobile-first layouts.
Firebase Auth
Email and password identity verification coupled with custom user claims managing member approval state.
Cloud Firestore
Document collections organized by calendar date keys, enabling efficient timeline rendering without heavy query sorting.
Firestore Security Rules
Declarative security rules preventing unapproved or unauthenticated users from reading or writing diary documents.
Core Engineering Modules & Workflows
Newly registered users enter a 'Pending' queue; administrators review user credentials before granting access to diary entries.
Entries are automatically partitioned and grouped by calendar date, creating a beautiful daily retrospective timeline.
Distraction-free text editor supporting emotion tags, author attribution, and rich-text reflection formatting.
Instant client-side filter engine allowing members to isolate entries by specific contributors or specific time periods.
Transparent member roster displaying active circle participants, approval statuses, and joining timelines.
Persistence Schemas & Execution Contracts
Database Schema & Entity Structure
users (collection)
└── {uid}: { email, displayName, status: "pending" | "approved", role: "member" | "admin", joinedAt }
DiaryEntries (collection)
└── {dateString}: {
entries: [
{ id, authorId, authorName, content, emotionTag, timestamp }
]
}Key Endpoints & Query Interfaces
Engineering Challenges & Specifications
Technical Obstacles Solved
Resolution: Wrote strict Firestore security rules enforcing request.auth != null && get(/databases/$(database)/documents/users/$(request.auth.uid)).data.status == 'approved'.
Resolution: Structured Firestore documents with date-keyed maps, eliminating client-side array sorting overhead during feed rendering.
Technology Stack Matrix
| Category | Tooling & Frameworks |
|---|---|
| Frontend Framework | React with TypeScript |
| Styling System | Tailwind CSS |
| Backend Platform | Google Firebase |
| Database | Cloud Firestore (NoSQL) |
| Authentication | Firebase Authentication |
| Deployment | Vercel Edge Network |