>CARGANDO // PROJECT DETAILS

PARSING ARCHITECTURE, DIAGRAMS & API ENDPOINTS

>CARGANDO // CARGANDO

INICIALIZANDO VISTA

Completadoreacttypescriptvitetailwindgogindocker

Generador de Currículums LaTeX

Creador de currículums enfocado en la privacidad que produce documentos LaTeX optimizados para ATS con plantillas modulares y compilación en tiempo real.

Problema y solución

Las herramientas convencionales almacenan datos sensibles en la nube y generan PDFs mal formateados que fallan en los filtros ATS. Esta solución garantiza privacidad local y salida LaTeX de precisión milimétrica.

Características

9 plantillas LaTeX optimizadas para sistemas ATS
Almacenamiento de estado local respetuoso con la privacidad
Vista previa en vivo con compilación en tiempo real en Go
Restricción estricta de formato a una página A4
Exportación directa a código fuente LaTeX y PDF

Stack tecnológico

Tecnología	Versión	Propósito	Por qué se eligió
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

Arquitectura

React 19 SPA

Zustand Store

localStorage

Live HTML Preview

LaTeX Generator

9 Template Engine

Gin Server

:8080

Rate Limiter

API Key Auth

Compile Handler

Tectonic

SQLite Stats

Prometheus

Grafana

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

Estructura del proyecto

backend

cmd

server

main.goGin server setup, routes, middleware

internal

compiler

handlers

middleware

websocket

frontend

src

components

editor

preview

hooks

stores

templates

Endpoints de API

Go Backend (puerto 8080)

Método	Ruta	Propósito
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

Diseño de base de datos

stats

2 cols

keyPK

TEXT

value

INTEGER

stats

Columna	Tipo	Notas
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.

Decisiones de diseño clave

Frontend-First Architecture

Decisión: All resume data, editing, preview, and LaTeX generation happen in the browser

Motivo: Privacy-first: all data stays in browser with localStorage persistence

Beneficios: Zero server costs for editing, user privacy, offline-capable editing

Compensaciones: No cloud sync, no cross-device access, localStorage size limits

Tectonic for LaTeX Compilation

Decisión: Use Tectonic instead of pdflatex or other TeX distributions

Motivo: Self-contained binary, no TeX distribution needed on the server

Beneficios: Simple Docker image, reproducible builds

Compensaciones: Slower than pdflatex for complex documents

Zustand over Redux/Context

Decisión: Use Zustand for state management with built-in persist middleware

Motivo: Minimal boilerplate, built-in localStorage persistence

Beneficios: Simple state management, easy persistence

Compensaciones: Less ecosystem than Redux

WebSocket for Compile Streaming

Decisión: Use WebSocket instead of HTTP polling for PDF compilation

Motivo: Real-time progress feedback improves UX during 5-60s compilation

Beneficios: User sees compilation stages (validating → writing → compiling → done)

Compensaciones: More complex than HTTP polling

Strategy Pattern for Templates

Decisión: Each template implements a Template interface with config, Preview, and generateLatex

Motivo: Multiple visual styles with shared data model

Beneficios: Extensible, each template self-contained, lazy-loadable via import.meta.glob

Compensaciones: Code duplication across templates

SQLite for Stats Only

Decisión: Use SQLite for aggregate visit/download counters only

Motivo: Zero-config embedded DB adequate for 2 counter rows

Beneficios: No external database dependency, simple deployment

Compensaciones: Write contention under concurrent access

Pruebas

None configured•0 pruebas unitarias

Qué se prueba

Cobertura faltante

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)

Desafíos clave

Compilar LaTeX en entornos serverless con tiempos de respuesta bajo 500ms
Garantizar que el contenido respete estrictamente los límites de una página A4

Aprendizajes clave

Integración de motores tipográficos LaTeX con microservicios web
Estrategias de renderizado local para máxima privacidad del usuario

>CARGANDO // PROJECT DETAILS

PARSING ARCHITECTURE, DIAGRAMS & API ENDPOINTS

Volver a proyectos

Demo en vivo Ver en GitHub

Completadoreacttypescriptvitetailwindgogindocker

Generador de Currículums LaTeX

Creador de currículums enfocado en la privacidad que produce documentos LaTeX optimizados para ATS con plantillas modulares y compilación en tiempo real.

Problema y solución

Características

9 plantillas LaTeX optimizadas para sistemas ATS
Almacenamiento de estado local respetuoso con la privacidad
Vista previa en vivo con compilación en tiempo real en Go
Restricción estricta de formato a una página A4
Exportación directa a código fuente LaTeX y PDF

Stack tecnológico

Tecnología	Versión	Propósito	Por qué se eligió
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

Arquitectura

React 19 SPA

Zustand Store

localStorage

Live HTML Preview

LaTeX Generator

9 Template Engine

Gin Server

:8080

Rate Limiter

API Key Auth

Compile Handler

Tectonic

SQLite Stats

Prometheus

Grafana

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

Estructura del proyecto

backend

cmd

server

main.goGin server setup, routes, middleware

internal

compiler

handlers

middleware

websocket

frontend

src

components

editor

preview

hooks

stores

templates

Endpoints de API

Go Backend (puerto 8080)

Método	Ruta	Propósito
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

Diseño de base de datos

stats

2 cols

keyPK

TEXT

value

INTEGER

stats

Columna	Tipo	Notas
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.

Decisiones de diseño clave

Frontend-First Architecture

Decisión: All resume data, editing, preview, and LaTeX generation happen in the browser

Motivo: Privacy-first: all data stays in browser with localStorage persistence

Beneficios: Zero server costs for editing, user privacy, offline-capable editing

Compensaciones: No cloud sync, no cross-device access, localStorage size limits

Tectonic for LaTeX Compilation

Decisión: Use Tectonic instead of pdflatex or other TeX distributions

Motivo: Self-contained binary, no TeX distribution needed on the server

Beneficios: Simple Docker image, reproducible builds

Compensaciones: Slower than pdflatex for complex documents

Zustand over Redux/Context

Decisión: Use Zustand for state management with built-in persist middleware

Motivo: Minimal boilerplate, built-in localStorage persistence

Beneficios: Simple state management, easy persistence

Compensaciones: Less ecosystem than Redux

WebSocket for Compile Streaming

Decisión: Use WebSocket instead of HTTP polling for PDF compilation

Motivo: Real-time progress feedback improves UX during 5-60s compilation

Beneficios: User sees compilation stages (validating → writing → compiling → done)

Compensaciones: More complex than HTTP polling

Strategy Pattern for Templates

Decisión: Each template implements a Template interface with config, Preview, and generateLatex

Motivo: Multiple visual styles with shared data model

Beneficios: Extensible, each template self-contained, lazy-loadable via import.meta.glob

Compensaciones: Code duplication across templates

SQLite for Stats Only

Decisión: Use SQLite for aggregate visit/download counters only

Motivo: Zero-config embedded DB adequate for 2 counter rows

Beneficios: No external database dependency, simple deployment

Compensaciones: Write contention under concurrent access

Pruebas

None configured•0 pruebas unitarias

Qué se prueba

Cobertura faltante

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)

Desafíos clave

Compilar LaTeX en entornos serverless con tiempos de respuesta bajo 500ms
Garantizar que el contenido respete estrictamente los límites de una página A4

Aprendizajes clave

Integración de motores tipográficos LaTeX con microservicios web
Estrategias de renderizado local para máxima privacidad del usuario