How and where should I update content in CV?

[Yuanhao-JIANG]

I want to change content in CV page, also delete the table of content.

But I notice there are
_layout/cv.html
_data/cv.yml
assets/json/resume.json

are these the right places to change? if so, what is the workflow for updating cv? (seems like change _data/cv.yml have no effect and changing assets/json/resume.json has some effects)

[george-gca]

_layouts/cv.html is responsible for rendering the contents of the cv. If you check here there is an unless condition with site.data.resume. Everything that is accessed via site. is defined in the _config.yaml. In this case, this information is defined here.

What this means is, if there is no resume data defined in _config.yml and loaded via a json file, it will load the contents of _data/cv.yml as fallback.

To remove the table of contents, simply remove the referred part from _layouts/cv.html.

[Weixiang-Sun]

U mean remove the whole sentence or just remove "unless", I try both but it failed to deploy.

[Yuanhao-JIANG]

remove the 'Table of contents' heading and the following unordered list in _layouts/cv.html

[xiong-zx]

I have noticed that there are many files and directories related to "CV", including:

• data/cv.yml
• _includes/cv/
• _includes/resume/
• pages/cv.md

What are the priorities of these files and directories? I suppose that there should be only one place to modify the cv.

[george-gca]

What do you mean by modifying the cv?

The only files responsible for the content of the cv are:

• data/cv.yml
• assets/json/resume.json

All the others are responsible for generating the needed html for visualizing the information.

The main one is assets/json/resume.json and it was introduced in #1547. It is a known standard for creating cv content in json format, so you could consume this data from various parsers and generate your cv programmatically.

As for data/cv.yml it was the original way of creating the content for the cv page, and it is currently used as a fallback if the file assets/json/resume.json is not found. Since it was already implemented and is more human readable than a json file we decided to keep it as an option.