Skip to main content

Header Commands

\cvname

Displays your name in large, bold text at the top of the CV. Signature:
\cvname{Name}
Name
string
required
Your full name
Example:
\cvname{Alya Pranata}
Output: Large, bold “Alya Pranata” in black color.

\cvtitle

Displays your professional title or tagline below your name. Signature:
\cvtitle{Title}
Title
string
required
Your professional title, role, or tagline. Can include \cvsep for separators.
Example:
\cvtitle{Software Engineer \cvsep Full-Stack and AI Enthusiast}
Output: Normal-sized text in header color with centered dot separator.

\cvsep

Inserts a centered dot separator (·) with proper spacing, commonly used in titles and metadata. Signature:
\cvsep
Example:
Software Engineer \cvsep Full-Stack Developer
Output: Software Engineer · Full-Stack Developer

\contactline

Displays a single line of contact information. Signature:
\contactline{Content}
Content
string
required
Contact information text. Can include \href{url}{text} for clickable links.
Examples:
\contactline{Bandung, Indonesia}
\contactline{+62 812 3456 7890}

Experience Command

\experienceitem

Formats a work experience entry with company, role, location, and dates. Signature:
\experienceitem{Company}{Role}{Location}{Dates}
Company
string
required
Company or organization name (displayed in bold)
Role
string
required
Job title or role (displayed in italics)
Location
string
required
Work location (city, remote, hybrid, etc.)
Dates
string
required
Employment period (e.g., “02/2025 - 07/2025” or “08/2024 - Present”)
Example:
\experienceitem
{Nusantara Digital Labs}
{Frontend Engineer Intern}
{Jakarta / Remote}
{02/2025 - 07/2025}

\begin{cvitems}
    \item Built internal dashboards using React and TypeScript, reducing manual reporting time by 30\%.
    \item Collaborated with designers and backend engineers to deliver reusable UI components and API integrations.
\end{cvitems}
Output Format:
  • Line 1: Company · Role
  • Line 2: Location · Dates (in smaller, header-colored text)

Education Command

\educationitem

Formats an education entry with institution, degree, and year. Signature:
\educationitem{Institution}{Degree}{Year}
Institution
string
required
School, university, or education provider name (displayed in bold)
Degree
string
required
Degree, program, or course name
Year
string
required
Graduation year or study period (e.g., “2021 - Present” or “2024”)
Examples:
\educationitem
{Institut Teknologi Bandung}
{B.S. in Computer Engineering}
{2021 - Present}
Output Format:
  • Line 1: Institution
  • Line 2: Degree (in smaller, header-colored text)
  • Line 3: Year (in smaller, header-colored text)

Projects Command

\projectitem

Formats a project entry with name, type, link, and year. Signature:
\projectitem{Name}{Type}{Link}{Year}
Name
string
required
Project name (displayed in bold)
Type
string
required
Project type or subtitle (displayed in italics)
Project URL. Use \href{url}{display text} format for clickable links.
Year
string
required
Project completion year
Examples:
\projectitem
{TaskFlow}
{Productivity Web App}
{\href{https://taskflow-demo.vercel.app}{taskflow-demo.vercel.app}}
{2025}

\begin{cvitems}
    \item Implemented Kanban task management with real-time updates and role-based access.
    \item Integrated authentication and activity logs for team collaboration workflows.
\end{cvitems}
Output Format:
  • Line 1: Name · Type
  • Line 2: Link - Year (in smaller, header-colored text)

Organization Command

\orgitem

Formats an organization involvement entry with name, role, location, and dates. Signature:
\orgitem{Organization}{Role}{Location}{Dates}
Organization
string
required
Organization or club name (displayed in bold)
Role
string
required
Your role or position (displayed in italics)
Location
string
required
Organization location
Dates
string
required
Involvement period
Example:
\orgitem
{Google Developer Student Clubs ITB}
{Core Team Member}
{Bandung, Indonesia}
{08/2022 - 07/2023}

\begin{cvitems}
    \item Facilitated Flutter and Firebase study sessions for 150+ students and prepared weekly learning materials.
    \item Coordinated the annual campus hackathon with 30 teams, including sponsorship outreach and mentor matching.
\end{cvitems}
Output Format: Same as \experienceitem
  • Line 1: Organization · Role
  • Line 2: Location · Dates (in smaller, header-colored text)

Awards Command

\awarditem

Formats an award or achievement entry with title, issuer, and year. Signature:
\awarditem{Title}{Issuer}{Year}
Title
string
required
Award or achievement title (displayed in bold)
Issuer
string
required
Issuing organization or institution
Year
string
required
Year received
Examples:
\awarditem
{Dean's List}
{School of Electrical Engineering and Informatics, ITB}
{2024}
Output Format:
  • Line 1: Title
  • Line 2: Issuer (in smaller, header-colored text)
  • Line 3: Year (in smaller, header-colored text)

Software Skills Command

\softitem

Formats a skill category with comma-separated skills. Signature:
\softitem{Category}{Skills}
Category
string
required
Skill category or domain (displayed in bold)
Skills
string
required
Comma-separated list of skills or tools
Example:
\softitem{Web}{React, Next.js, Node.js, TypeScript, Tailwind CSS}
\softitem{Data/AI}{PostgreSQL, MongoDB, Pinecone, OpenAI API}
\softitem{Tools}{Git, Linux, Docker, Vercel, Figma}
Output Format:
  • Line 1: Category
  • Line 2: Skills (in smaller, header-colored text)

cvitems Environment

The cvitems environment creates bullet-point lists for describing achievements, responsibilities, or project details. Signature:
\begin{cvitems}
    \item First bullet point
    \item Second bullet point
    \item Third bullet point
\end{cvitems}
Used With:
  • \experienceitem
  • \projectitem
  • \orgitem
Styling:
  • Small font size
  • Header color (gray)
  • Compact spacing between items
  • Slight left indentation
Example:
\experienceitem
{PT Data Sistem Integrasi}
{Software Engineer Intern}
{Bandung, Indonesia}
{08/2024 - 12/2024}

\begin{cvitems}
    \item Developed RESTful endpoints with Node.js and PostgreSQL for inventory and order tracking.
    \item Wrote test cases and improved query performance for high-traffic pages.
\end{cvitems}

Command Definition Source

All commands are defined in the preamble of the template files (lines 73-119 in both cv_en.tex and cv_id.tex):
\newcommand{\cvname}[1]{\noindent{\LARGE\bfseries\color{black} #1}\par}
\newcommand{\cvtitle}[1]{\noindent{\normalsize\color{headercolor} #1}\par\vspace{0.5em}}
\newcommand{\cvsep}{\hspace{0.35em}\textcolor{headercolor}{\textperiodcentered}\hspace{0.35em}}

\newcommand{\experienceitem}[4]{%
	\noindent\textbf{#1}\cvsep\textit{#2}\\
	\noindent{\small\color{headercolor}#3\cvsep#4}\par\vspace{0.7em}
}

\newcommand{\educationitem}[3]{%
	\noindent\textbf{#1}\\
	{\noindent\small\color{headercolor}#2\\}
	{\noindent\small\color{headercolor}#3\par}\vspace{0.7em}
}

\newcommand{\projectitem}[4]{%
	\noindent\textbf{#1}\cvsep\textit{#2}\\
	\noindent{\small\color{headercolor}#3 - #4}\par\vspace{0.7em}
}

\newcommand{\orgitem}[4]{%
	\noindent\textbf{#1}\cvsep\textit{#2}\\
	\noindent{\small\color{headercolor}#3\cvsep#4}\par\vspace{0.7em}
}

\newcommand{\awarditem}[3]{%
	\noindent\textbf{#1}\\
	{\noindent\small\color{headercolor}#2\\}
	{\noindent\small\color{headercolor}#3\par}\vspace{0.7em}
}

\newcommand{\softitem}[2]{%
	\noindent\textbf{#1}\\
	{\noindent\small\color{headercolor}#2\par}\vspace{0.7em}
}

\newcommand{\contactline}[1]{\noindent #1\par\vspace{0.15em}}

\newenvironment{cvitems}{%
	\begin{itemize}[leftmargin=1.25em, itemsep=0.2em, topsep=0.3em]
	\small\color{headercolor}
}{%
	\end{itemize}\vspace{0.2em}
}

Build docs developers (and LLMs) love