How nathanblatter/personal-site works
This is a personal portfolio and services site with a React frontend, FastAPI API, and PostgreSQL-backed content. The principal visitor workflow is route selection, page rendering, and API-backed content display; the admin side edits portfolio and consulting data. The repository also includes a journal processing subsystem and file storage. Several backend capabilities are visible in the tree and source index but not sampled, so their internal relationships are omitted unless documented or indexed.
Main entry points: database.py Database sessions · main.py HTTP application · crm.py Consulting CRM · journal.py Journal API
Components 22
Portfolio frontend
- Route application
frontend/src/App.tsx - Portfolio pages
frontend/src/pages - Admin workspace
frontend/src/pages/Admin.tsx - API client
frontend/src/lib/api.ts
Backend API
- HTTP application
backend/app/main.py - Admin authentication
backend/app/auth.py
Content and consulting
- Portfolio content routes
backend/app/routers/about.py - Services content
backend/app/routers/services.py - Consulting CRM
backend/app/routers/crm.py - API data schemas
backend/app/schemas.py
Journal system
- Journal API
backend/app/routers/journal.py - Journal worker
backend/app/journal_worker.py - Vocabulary pipeline
backend/app/vocab_service.py - Vocabulary seed
backend/app/journal_vocab.py
Shared services
- Object storage API
backend/app/routers/storage.py - Database sessions
backend/app/database.py - Domain models
backend/app/models.py - Response cache
backend/app/cache.py
Other components
- Site visitor
- Site administrator
- PostgreSQL
- S3-compatible storage
Connections 25
- Site visitor → Route application: opens site
frontend/src/App.tsx - Site administrator → Admin workspace: manages content
- Route application → Portfolio pages: routes to
frontend/src/App.tsx - Portfolio pages → API client: requests content
frontend/src/lib/api.ts - Admin workspace → API client: submits changes
- API client → HTTP application: calls API
README.md - HTTP application → Portfolio content routes: registers routes
backend/app/main.py - HTTP application → Services content: registers routes
backend/app/main.py - HTTP application → Consulting CRM: registers routes
backend/app/main.py - Portfolio content routes → Database sessions: queries data
- Services content → Database sessions: queries and updates
backend/app/routers/services.py - Services content → Response cache: invalidates cache
backend/app/routers/services.py - Consulting CRM → Database sessions: uses sessions
backend/app/routers/crm.py - Consulting CRM → Domain models: uses models
backend/app/routers/crm.py - Consulting CRM → API data schemas: uses schemas
backend/app/routers/crm.py - Database sessions → PostgreSQL: connects
README.md - Domain models → Database sessions: uses base
backend/app/models.py - Journal API → Vocabulary pipeline: uses vocabulary
backend/app/routers/journal.py - Journal API → Object storage API: uses storage
backend/app/routers/journal.py - Journal worker → Vocabulary pipeline: extracts candidates
backend/app/journal_worker.py - Journal worker → Journal API: references API
backend/app/journal_worker.py - Vocabulary pipeline → Vocabulary seed: uses seed terms
backend/app/vocab_service.py - Object storage API → S3-compatible storage: stores and lists files
backend/app/routers/storage.py - Journal API → Admin authentication: checks access
backend/app/routers/journal.py - Object storage API → Admin authentication: checks access
backend/app/routers/storage.py