LaTeX CV Template Guide (Enterprise)
Advanced guide to Vitae’s LaTeX template editor: placeholders, compile workflow, and enterprise-grade customization. Requires Enterprise plan.
LaTeX templates for complete beginners (Enterprise)
This guide is a practical noob playbook. If you have never edited a LaTeX template before, follow the steps in order and you will produce a working custom template safely.
Requires Enterprise plan.
Before you start: the safest workflow
Do not start from a blank file. In Vitae, the safest route is:
- Open Templates.
- Pick a standard template that is close to your desired style.
- Click Fork to create your own editable copy.
- Open the fork in the LaTeX editor.
Step 1: Understand .tex vs .sty (this is critical)
In the editor, you can switch between two files:
- .tex = your CV layout skeleton (header, sections, placeholders)
- .sty = styling commands that define how blocks render (experience entries, project rows, spacing, typography)
Rule of thumb: change .tex for structure and section flow; change .sty for visual behavior and command styling.
Step 2: Use placeholders correctly
Vitae injects candidate data through placeholders. Keep placeholders intact, and move them where you want content to appear.
%%firstname%% %%lastname%%
%%professionaltitle%%
%%summary%%Most-used scalar variables
%%firstname%%,%%lastname%%%%email%%,%%phone%%,%%linkedin%%%%location%%,%%professionaltitle%%,%%summary%%
Most-used block variables
%%experience_block%%%%education_block%%%%skills_block%%%%certifications_block%%%%projects_block%%%%languages_block%%
Step 3: Add logo and brand color
In the left branding panel, configure the accent color and logo visibility. In LaTeX mode, this maps to key placeholders and toggles:
%%companylogo%%— injects your organisation logo in the header%%primary_color_hex%%— drives accent color in templates that support itshow_logotoggle — controls whether logo is rendered
If logo is not showing, first check the toggle and then verify your template includes%%companylogo%% in the header section.
Step 4: Build your first working template (10-minute path)
Start by editing only the header and section order. Keep all existing block placeholders. Save, preview, and iterate in small changes.
\begin{center}
%%companylogo%%
{\LARGE\bfseries %%firstname%% %%lastname%%}\\
{\large %%professionaltitle%%}
\end{center}
\section*{Experience}
%%experience_block%%
\section*{Education}
%%education_block%%Step 5: Save and preview loop
After each meaningful edit, click Save and check the PDF preview. Validate with at least two candidate shapes:
- Short profile (1 page, sparse content)
- Long profile (multi-page, dense experience/projects)
Step 6: Troubleshooting for noobs
Problem: PDF preview fails after edit
Undo the last change, save again, then re-introduce edits in smaller chunks.
Problem: Candidate data not appearing
Check placeholder spelling exactly. %%firstname%% works; typos like%%first_name%% will not.
Problem: Logo does not render
Confirm three things: logo is uploaded, show_logo is enabled, and your .tex includes %%companylogo%%.
Problem: Colors do not change
Ensure your template actually uses %%primary_color_hex%%(or mapped color variable) in color definitions.
Step 7: Publish an enterprise-safe version
After validation, publish the template version and tag intended use-cases (industry segment, seniority band, or client-specific presentation requirements).
Regular template vs LaTeX template
| Dimension | Regular Template | LaTeX Template |
|---|---|---|
| Setup speed | Fast | Moderate |
| Layout control | Standard | Full |
| Best for | Team-wide consistency | Advanced enterprise customization |
Recommended screenshots for this guide
- Templates list showing standard template and Fork action
- Template editor with .tex and .sty file switcher visible
- Variable explorer panel (scalar + block placeholders)
- Branding panel (logo toggle + accent color)
- PDF preview before/after a header change
- Published template confirmation with version context
Operational best practices
- Keep a controlled set of approved enterprise templates to prevent governance drift.
- Validate every template against multiple CV lengths before production rollout.
- Document placeholder conventions in your implementation playbook for onboarding speed.