How sb2nov/resume works
Project type and purpose
• This is an open-source LaTeX resume template project. Its purpose is to provide a single-page, one-column resume format for software developers, with a clear structure (education, experience, projects) and easy customization via LaTeX commands and templates.
File structure
• Top-level files:
• sourabh_bajaj_resume.tex – the main LaTeX source
• build.sh – a simple shell script to build locally
• Dockerfile – defines a containerized LaTeX build environment
• .github/workflows/docker-image.yml – GitHub Actions CI pipeline
• Other files:
• README.md – project description and instructions
• LICENSE, .gitignore – project metadata
• resume_preview.png – preview artifact (referenced in README)
• PDF and TeX resume in root
README for additional insights
• Describes motivation, quick start, Docker-based build instructions, and Overleaf link.
Main components of the system
a. Developer Workstation (Local Environment)
• Source files (.tex, images, shell script)
• Local build script (build.sh)
b. Containerized Build Environment
• Docker image (LaTeX toolchain)
• Dockerfile definition
c. Continuous Integration (GitHub Actions)
• Workflow defined in .github/workflows/docker-image.yml
• Steps: checkout → build Docker image → run pdflatex → store artifacts
d. Artifacts / Outputs
• sourabh_bajaj_resume.pdf
• resume_preview.png (preview)
e. External Services
• Docker Hub (optional push/pull of LaTeX image)
• Overleaf (hosted template link, optional external integration)
Relationships and interactions
• Developer edits .tex and runs ./build.sh locally → invokes Docker container → runs pdflatex → outputs PDF.
• On push to GitHub: GitHub Actions triggers → uses Dockerfile to build image → runs LaTeX compile → uploads PDF as CI artifact (or deploys).
• Optionally, users import the template into Overleaf via a link.
Architectural patterns and design principles
• Separation of concerns: source content (TeX) is separate from build logic (shell script, Dockerfile).
• Containerization: Ensures reproducible builds across environments.
• CI/CD pipeline: Automates validation and artifact generation on each push.
Must-have elements
• Clear labels on all containers, subprocesses, and artifacts