How jhonson-lc/blog-fisei works
Project Type and Purpose
• This is a monorepo‑based full‑stack web application:
• Frontend: Next.js (TypeScript, App Router, SSR/SSG)
• Backend/CMS: Strapi (Node.js, REST API, content‑type driven)
• Shared Packages: UI components, ESLint/TSConfig presets
• Tooling: pnpm workspace, Turbo (build orchestration)
Main Components
• Client Application (apps/client)
• Server Application / CMS (apps/server)
• Database (PostgreSQL/MySQL/SQLite via Strapi config)
• File Storage (local “public/uploads” or external object storage)
• Shared Package Libraries (packages/ui, packages/eslint‑config‑custom, packages/tsconfig)
• Developer Tooling (pnpm, Turbo, CI/CD)
Relationships & Data Flow
A. Client ↔ Server
• Next.js pages/components invoke Strapi REST API endpoints (e.g., /api/article, /api/author) to fetch content.
• Data flows client ← server as JSON; server may authenticate requests or enforce middleware.
B. Server ↔ Database
• Strapi controllers/services perform CRUD on the database based on defined schemas.
C. Server ↔ Storage
• File uploads saved under apps/server/public/uploads (or proxied to S3).
D. Monorepo Packages ↔ Apps
• apps/client imports UI components from packages/ui.
• Both apps adhere to shared linting and TS config in packages/eslint‑config‑custom and packages/tsconfig.
E. Developer Workflow
• Turbo orchestrates builds, tests, and lint tasks across all packages.
Architectural Patterns & Design Principles
• Separation of Concerns: UI vs. API vs. Data Storage.
• Modular Monorepo: shared packages for UI, lint, TS settings.
• Layered MVC‑style structure inside Strapi: content-types → controllers → services → routes.
• Next.js App Router with server/client components.
• Infrastructure‑agnostic: environment variables drive database & storage configuration.