Content Guide

This file is the fastest way to find where to edit content in this site.

Quick Map

Common Tasks

1. Update homepage text

Edit _pages/about.md.

Typical sections there:

  • intro text
  • highlights
  • academic background cards
  • research interests
  • news list

2. Change CV content

Edit _pages/cv.md.

This page contains:

  • education
  • work experience
  • skills
  • CV publications block

3. Add a new publication

Add a new markdown file in _publications/.

Existing files there are your template examples.

4. Add a new project

Add a new markdown file in _projects/.

5. Add a new footprint / travel note

Add a new markdown file in _plogs/.

Filename format should stay date-based, like:

2026-03-29-city-name.md

6. Change menu items

Edit _data/navigation.yml.

Edit _config.yml.

Look for:

  • title
  • author.avatar
  • author.avatar_options
  • author.name
  • author.location
  • author.employer
  • author.github
  • author.googlescholar
  • author.linkedin

8. Replace or add an image

Put the image in images/.

Then reference it from markdown using:

![Alt text](../images/example.png)

9. Add a PDF / video / attachment

Put the file in files/, then link it directly.

10. Change styles

Most custom appearance now lives in _sass/_theme.scss.

Use these files when needed:

11. Change interactions

Use assets/js/:

Editing Rules For Future You

  • If you want to change words, start with _pages, _projects, _publications, or _plogs.
  • If you want to change the page frame, start with _layouts/page-content.html, _layouts/section-list.html, or _layouts/travel-log-entry.html.
  • If you want to change reusable UI blocks, start with _includes.
  • If you want to change global style, start with _sass/_site-visual-theme.scss.
  • If you want to change site-wide identity, start with _config.yml.

Files You Usually Do Not Need To Touch

  • _site/: generated output
  • vendor/: dependencies
  • tmp/: temporary storage
  • .DS_Store files: ignore them

Suggested Future Cleanup

  • Remove tracked .DS_Store files outside images/ as well.
  • Replace the generic upstream README with project-specific maintenance notes.
  • Add one reusable template file for new publications / projects / plogs.