JK
>LADDAR // LADDAR
INITIERAR VY
Slutförtreacttypescriptvitetailwindgogindocker
LaTeX CV-generator
Verktyg för CV-skapande med fokus på integritet som genererar ATS-optimerade LaTeX-dokument.
Problem och lösning
Vanliga CV-verktyg lagrar känsliga uppgifter i molnet och producerar PDF-filer som fallerar i ATS-system.
Funktioner
- 9 optimerade LaTeX-mallar för ATS-system
- Lokal lagring i webbläsaren för maximal integritet
- Liveförhandsgranskning med realtidskompilering i Go
- Strikt begränsning till exakt en A4-sida
- Export till LaTeX-källkod och färdig PDF
Teknikstack
| Teknik | Version | Syfte | Varför vald |
|---|---|---|---|
| React | 19 | UI framework | Latest concurrent features, lazy loading |
| TypeScript | ~6.0 | Type safety | Prevents runtime errors on complex resume data model |
| Vite | 8.x | Build tool & dev server | Fast HMR, native ESM, code splitting via glob imports |
| Tailwind CSS | v4 | Utility-first styling | Rapid UI development, consistent design tokens |
| Zustand | 5.x | State management | Minimal boilerplate, built-in persist middleware |
| @dnd-kit | core 6, sortable 10 | Drag-and-drop | Accessible, performant sortable lists |
| Go | 1.25+ | Backend runtime | Fast startup, small binaries, excellent concurrency |
| Gin | 1.12 | HTTP framework | High performance, middleware ecosystem |
| Tectonic | 0.16.9 | LaTeX→PDF compiler | Self-contained, no TeX distribution needed |
| Docker | — | Containerization | Reproducible builds, production parity |
| SQLite | modernc.org/sqlite 1.54 | Stats persistence | No CGO dependency, cross-compilation |
| Sentry | 10.x | Error tracking & monitoring | Session replay, performance monitoring, feedback widget |
Arkitektur
Frontend (React SPA)
- React 19 SPA with Zustand state management
- 9 pluggable template strategy pattern (config + preview + LaTeX generator)
- Live A4 page simulation with zoom and pagination
- WebSocket-based real-time compilation streaming
- Vite 8 with code splitting via import.meta.glob
Backend (Go Microservice)
- Go/Gin HTTP server with single concern: LaTeX compilation
- Tectonic subprocess management with --untrusted sandboxing
- Per-IP token bucket rate limiting (5 rps, burst 10)
- API key authentication on compile endpoints
- SQLite for aggregate visit/download statistics
Infrastructure
- Docker Compose orchestration (backend + Prometheus + Grafana)
- Multi-stage Docker builds (golang → alpine + tectonic)
- Vercel deployment for frontend, Render for backend
- Prometheus metrics with Grafana dashboards
Projektstruktur
backend
cmd
server
main.go
internal
compiler
handlers
middleware
websocket
frontend
src
components
editor
preview
hooks
stores
templates
API-slutpunkter
Go Backend (port 8080)
| Metod | Rutt | Syfte |
|---|---|---|
| POST | /api/compile | Compile LaTeX to PDF (HTTP) |
| GET | /api/compile/ws | WebSocket compile with progress streaming |
| POST | /api/stats/visit | Record page visit |
| POST | /api/stats/download | Record PDF download |
| GET | /api/stats | Get aggregate stats |
| GET | /api/health | Health check (Tectonic + DB status) |
| GET | /metrics | Prometheus metrics |
Databasdesign
stats
| Kolumn | Typ | Anteckningar |
|---|---|---|
| keyPK | TEXT | Counter name: 'visits' or 'downloads' |
| value | INTEGER | Counter value, default 0 |
Single table with 2 key-value rows. WAL mode enabled. Used only for aggregate visit/download statistics — no user data stored.
No relationships. Single table with 2 counter rows.
Viktiga designbeslut
Frontend-First Architecture
Beslut: All resume data, editing, preview, and LaTeX generation happen in the browser
Varför: Privacy-first: all data stays in browser with localStorage persistence
Fördelar: Zero server costs for editing, user privacy, offline-capable editing
Avvägningar: No cloud sync, no cross-device access, localStorage size limits
Tectonic for LaTeX Compilation
Beslut: Use Tectonic instead of pdflatex or other TeX distributions
Varför: Self-contained binary, no TeX distribution needed on the server
Fördelar: Simple Docker image, reproducible builds
Avvägningar: Slower than pdflatex for complex documents
Zustand over Redux/Context
Beslut: Use Zustand for state management with built-in persist middleware
Varför: Minimal boilerplate, built-in localStorage persistence
Fördelar: Simple state management, easy persistence
Avvägningar: Less ecosystem than Redux
WebSocket for Compile Streaming
Beslut: Use WebSocket instead of HTTP polling for PDF compilation
Varför: Real-time progress feedback improves UX during 5-60s compilation
Fördelar: User sees compilation stages (validating → writing → compiling → done)
Avvägningar: More complex than HTTP polling
Strategy Pattern for Templates
Beslut: Each template implements a Template interface with config, Preview, and generateLatex
Varför: Multiple visual styles with shared data model
Fördelar: Extensible, each template self-contained, lazy-loadable via import.meta.glob
Avvägningar: Code duplication across templates
SQLite for Stats Only
Beslut: Use SQLite for aggregate visit/download counters only
Varför: Zero-config embedded DB adequate for 2 counter rows
Fördelar: No external database dependency, simple deployment
Avvägningar: Write contention under concurrent access
Tester
None configured•0 enhetstester
Vad som testas
Saknad täckning
- Unit tests for escapeLatex, generateLatex functions
- Unit tests for template rendering and LaTeX generation
- Integration tests for compile handler
- Integration tests for WebSocket compilation flow
- E2E tests for critical user flows (edit → preview → export)
Viktiga utmaningar
- LaTeX compilation timeout (Tectonic can take 60+ seconds for complex documents)
- Profile image size in request body increasing payload and compilation time
- localStorage quota limits (~5MB) for saved resume versions
- Multi-page PDF warning — preview is approximate, actual PDF may differ
- Concurrent compilation on single-container deployment
Viktiga lärdomar
- Strategy pattern for pluggable template architecture
- WebSocket streaming for real-time compilation progress
- LaTeX escaping with null-byte placeholders to prevent double-escaping
- Multi-page preview simulation with section-aware pagination
- Frontend-first architecture trade-offs (privacy vs. no cloud sync)