How johannesbremer/praxisplaner works
Project Type & Purpose
• From the file tree, we see a React/TypeScript front-end (components/, src/) with SSR (src/ssr.tsx), a Convex backend (convex/), GitHub CI workflows, and static assets (public/).
• This is a full-stack application (“Praxisplaner”) using a component-based UI library, server-side rendering, and a serverless database/backend (Convex).
File Structure Highlights
• components/ui: Reusable UI building blocks (buttons, dialogs, cards, etc.).
• src/
• client.tsx: Client bootstrap for CSR.
• ssr.tsx: Entry for server-side rendering.
• router.tsx + src/routes: Route definitions & pages.
• src/db/schema.ts: Local type definitions mirroring your data model.
• convex/: Serverless functions & schema delivering real-time data, user preferences, logs.
• CI/CD: .github/workflows CI, code scanning.
Key Architecture Components
a. Frontend UI Layer
• Browser executes client bundle (React components, router).
• SSR server pre-renders pages on request (using ssr.tsx).
b. Server-Side Render Engine
• Node.js server (or adapter) invokes React SSR entry, serves HTML + initial data.
c. Convex Backend
• Serverless functions (gdtFiles, gdtPreferences, permissionLogs) implement business logic.
• Convex-managed database stores schema.ts data models.
• Real-time subscriptions push updates to client.
d. Static Asset Hosting
• public/ files served via CDN or static server.
e. CI/CD Pipeline
• GitHub Actions build, lint (eslint, prettier), test, and deploy both front and back.
a. Components & Boundaries
• Client Browser (UI Components)
• SSR Server (ssr.tsx entry)
• Convex API Gateway
• Convex Functions & Database
• Static Asset Host/CDN
• GitHub CI/CD
b. Interactions & Data Flow
1. Browser → SSR Server: HTTP GET page → server-rendered HTML + JS.
2. Browser ↔ Convex:
• Queries & Mutations via Convex client in src/client.tsx.
• Real-time subscriptions on data changes.
3. SSR Server → Convex:
• Pre-fetch data on SSR page render.
4. CI/CD → Deployment Targets (Frontend host, Convex functions).
c. Architectural Patterns
• Component-based UI (Atomic Design in components/ui).
• Universal/Isomorphic rendering via SSR.
• Serverless functions + real-time DB (Convex).
• Separation of concerns: UI / routing / data / styles.
d. Technologies & Frameworks
• React, TypeScript, CSS/PostCSS, pnpm.
• Convex for backend & DB.
• GitHub Actions for CI/CD.
• ESLint, Prettier for code quality.