ARCHITECTURE_PLAN.md

🧠 Technobyte Blogging System - Architecture Plan

🎯 Goal

To build a scalable, zero-cost, Git-based blogging platform where:

• Members write blogs
• Content is reviewed via PR
• Blogs are published via static site generation

---

🏗️ High-Level Architecture

Content Layer (GitHub) ↓ Validation Layer (GitHub Actions) ↓ Build Layer (Next.js SSG) ↓ Hosting Layer (Vercel) ↓ End Users (Web)

---

📦 Data Model

Blog

• Stored as Markdown (index.md)
• Contains frontmatter + content

Author

• Stored as JSON
• Referenced via ID

Category

• Stored as JSON
• Fixed taxonomy

---

🔗 Relationships

• Blog → Authors (many-to-many)
• Blog → Category (one-to-one)
• Blog → Tags (many)
• Blog → Series (optional)

---

📁 Storage Strategy

• Blogs are folder-based
• Assets are colocated with blogs
• Common assets are in /public

---

⚙️ Rendering Strategy

• Next.js Static Site Generation (SSG)
• Markdown → HTML transformation
• Frontmatter parsing
• Dynamic routing using slug

---

🔐 Access Control

• Write access: internal members (via GitHub)
• Read access: public

---

🔄 Content Flow

Contributor → PR → Validation → Review → Merge → Deploy

---

🚀 Scalability Considerations

• Handles 1000+ blogs (file-based system)
• No database dependency
• Easy caching via static hosting

---

⚠️ Risks

• Reviewer bottleneck
• Content inconsistency
• Repo size growth (images)

---

🔮 Future Enhancements

• Search (Algolia)
• Comments (Giscus)
• Analytics
• Author dashboards
• CMS (optional)

---

This system treats content as code and leverages Git as the database.