Sections & entries
The sections field is an ordered list. Each section has a type, a title, and a list of entries, the roles, degrees, projects, or skill groups it contains.
#The section object
| Field | Type | Description |
|---|---|---|
typeoptional | SectionType | One of the five section types below. Defaults to custom. |
titleoptional | string | The heading shown above the section, e.g. "Experience". |
entriesoptional | Entry[] | The items in this section, rendered in order. |
#Section types
There are five:
| Field | Type | Description |
|---|---|---|
experienceoptional | SectionType | Jobs and roles. Title = role, subtitle = company. |
educationoptional | SectionType | Degrees and schools. Title = degree, subtitle = school. |
skillsoptional | SectionType | Skill groups. Title = category, description or bullets = the skills. |
projectsoptional | SectionType | Projects and side work. |
customoptional | SectionType | Anything else, awards, publications, a summary. The default. |
#The entry object
Every entry, in every section type, uses the same fields:
| Field | Type | Description |
|---|---|---|
titlerequired | string | The primary line, a role, a degree, a project, a skill category. |
subtitleoptional | string | A secondary line, usually a company or school. |
startDateoptional | string | When it started. Free text, e.g. "2021" or "Jan 2021". |
endDateoptional | string | When it ended, or "Present". |
descriptionoptional | string | A short paragraph under the entry. |
bulletsoptional | string[] | A list of accomplishment bullets. |
#Example
a section
- type: experience title: Experience entries: - title: Senior Software Engineer subtitle: Acme Cloud startDate: 2021 endDate: Present bullets: - Led the migration to a typed API layer. - Mentored three engineers to senior. - title: Software Engineer subtitle: Northwind startDate: 2018 endDate: 2021 bullets: - Shipped the billing rewrite.