Back to blog
Technical NoteMay 16, 2026

Resume in LaTeX: Treating a CV as Source-Controlled Design

A LaTeX resume project that uses reusable commands, typography, spacing, and version control to keep a technical CV maintainable.

LaTeXResumeDesignDocumentation

The Resume repo keeps a CV as code. Instead of editing a visual document by hand, the resume is written in LaTeX with reusable commands for sections, projects, education, work experience, and layout.

This is a small project, but it reflects a useful engineering habit: documents that change often can benefit from structure and version control.

Document System

The LaTeX source uses packages for page geometry, fonts, color, section titles, tables, list spacing, icons, and links. Custom commands help keep entries consistent across the document.

That consistency matters. A resume needs to be easy to scan, and small spacing differences can make the whole page feel less professional.

Information Architecture

The content emphasizes education, experience, projects, technical skills, and achievements. A strong technical resume is not just a list of tools; it shows what was built, what stack was used, and what impact the work had.

Sensitive contact or referee details should be handled carefully when a resume is public, which is one reason source control hygiene matters.

Knowledge Points

  • LaTeX is strong for precise typography and repeatable document generation.
  • Custom commands reduce formatting drift across resume sections.
  • Version control makes it easy to track changes for different job applications.
  • A technical CV should connect skills to concrete projects and outcomes.
  • Layout density should support scanning rather than squeezing in every detail.
  • Public repositories should avoid exposing private referee or contact details unnecessarily.
  • Treating writing as code encourages review, iteration, and reuse.

Takeaway

This repo shows that engineering thinking applies to personal documents too. A resume becomes easier to maintain when layout, content, and structure are separated.

这个简历仓库把 CV 当代码来维护。不是手动编辑可视化文档,而是用 LaTeX 写简历,为章节、项目、教育经历、工作经历和排版定义可复用的命令。

这是个小项目,但它反映了一个实用的工程习惯:经常变动的文档可以从结构化和版本控制中受益。

文档系统

LaTeX 源文件使用了页面几何、字体、颜色、章节标题、表格、列表间距、图标和链接等包。自定义命令帮助保持文档中各条目格式的一致性。

这种一致性很重要——简历需要容易浏览,细微的间距差异就可能让整个页面感觉不够专业。

信息架构

内容重点突出教育经历、工作经验、项目、技术技能和成就。一份好的技术简历不只是工具列表,它展示了构建了什么、使用了什么技术栈,以及工作产生了什么影响。

当简历公开时,敏感的联系方式或推荐人信息应该谨慎处理,这也是版本控制卫生很重要的原因之一。

知识点

  • LaTeX 在精确排版和可重复文档生成方面非常强大。
  • 自定义命令减少了简历各节之间的格式漂移。
  • 版本控制让针对不同职位申请的改动追踪变得简单。
  • 技术简历应该把技能与具体项目和成果联系起来。
  • 排版密度应该支持快速浏览,而不是把所有细节都塞进去。
  • 公开仓库应该避免不必要地暴露推荐人或私人联系信息。
  • 把写作当代码对待,鼓励审查、迭代和复用。

总结

这个仓库说明工程思维也适用于个人文档。当排版、内容和结构分离时,简历更容易维护。