Our website is located at https://chinacomx.github.io and built by damianodamiani with Gemini 3.1 Pro. It uses GitHub Pages and the Hugo framework paired with the Blowfish theme.
To preview and work on the website on your computer, you no longer need Ruby or Jekyll. Instead, you need to install Hugo (Extended Version).
You only need to do this once.
For macOS:
Use homebrew to install Hugo:
brew install hugo
(Note: Homebrew automatically installs the extended version on macOS).
For Windows: We recommend using Chocolatey:
choco install hugo-extended
If you run into issues, please check the full installation instructions by Hugo.
To help you navigate the repository, here is an overview of where everything lives:
chinacomx.github.io/
├── .github/
│ └── workflows/
│ └── hugo.yaml <-- The script that builds our live site
|── archetypes/ <-- Hugo settings
├── assets/ <-- Here are global images (like the logos)
│ └── css/
│ └── custom.css <-- Our custom CSS file for some minor changes to the theme
├── config/
│ └── _default/ <-- Here are the global site settings and menu .toml files (key for updating the theme)
├── content/
│ └── activities/ <-- ALL ACTIVITIES & POSTS GO HERE
│ │
│ ├── 2026-04-12-Past-Event/ <-- Example of a "Page Bundle" folder
│ │ ├── index.md <-- The actual text of your post
│ │ └── feature.jpg <-- The main thumbnail/header image
│ │
│ └── 2026-05-04-CfPChineseSW/ <-- Example of a "Page Bundle" folder
│ ├── index.md <-- The actual text of your post
│ ├── feature.jpg <-- The main thumbnail/header image
│ └── extra-image.png <-- Any other images used in the text
│ └── ...
│ └── _index.md <-- Standalone page: "Activities"
│ └── team/ <-- Folder for team member profiles
│ └── _index.md <-- Standalone page: "Team"
│ └── aijia.md <-- Subpage for Aijia, here you can edit your profile page
│ └── astrid.md <-- Subpage for Astrid, here you can edit your profile page
│ └── damian.md <-- Subpage for Damian, here you can edit your profile page
│ └── jiu.md <-- Subpage for Jiu, here you can edit your profile page
│ └── lena.md <-- Subpage for Lena, here you can edit your profile page
│ └── _index.md <-- The splash page content
│ └── about.md <-- Standalone page: "About"
│ └── contact.md <-- Standalone page: "Contact"
│ └── publications.md <-- Standalone page: "Publications"
│ └── resources.md <-- Standalone page: "Resources"
├── data/ <-- Empty
├── i18n/ <-- Here are the language files, for later to change if we add other languages
├── public/ <-- The public files for the live website build (create automatically when deployed)
├── resources/ <-- The resources files for the live website build (create automatically when deployed)
├── static/ <-- Files that copy exactly as-is (like favicon.ico)
├── themes/ <-- Hugo blowfish theme files
└── .nojekyll <-- Tells GitHub to use Hugo instead of Jekyll
As a content editor, you will spend 99% of your time inside the content/activities/ folder. If you want to update your profile or any other part of the website, you can also do so via a new PR.
Understanding the Page Bundle:
Notice how 2026-05-04-CfPChineseSW is a folder, not just a single file. By keeping the index.md text file and the feature.jpg image inside the exact same folder, Hugo knows they belong together. You never have to worry about complex image linking—just drop the image in the folder and type  in your markdown.
If you have the necessary tools installed, check out this repo in GitHub Desktop (or your preferred Git client), open it in your Terminal, and type the following:
hugo server
You should see something like this:
Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)
Press Ctrl+C to stop
Open http://localhost:1313 in your browser. The site will automatically refresh in real-time as you save changes to your files! Press ctrl-c in the terminal to stop the local server.
Other than with Jekyll, we use a Page Bundle structure in Hugo. This keeps all text and images for a single activity organized in one specific folder.
- Inside the
content/activities/folder, create a new folder. Name it using the patternYYYY-MM-DD-ShortTitle.
- Example:
2026-05-04-CfPChineseSW
- Inside this new folder, create a Markdown file named
index.md. All of the post's written content goes in here. - Place the image that will accompany the post into this exact same folder. Name this main image
feature.jpg(orfeature.png, etc.). The theme will automatically detect it and use it as the post's cover/thumbnail.
Make sure to always include this header configuration (called "Front Matter") at the very top of your index.md file. Adjust the title and date fields accordingly for each new post:
---
title: "Call for Papers for the edited volume CHINESE STAR WARS: VERNACULAR READINGS OF A GLOBAL MULTIMEDIA PHENOMENON"
date: 2026-05-04
type: "article"
---
As a rule, we do not add edits directly onto the main branch.
- Create a Branch: Always create a new branch and name it in such a way that tracing it back is easy (e.g.,
add-star-wars-cfp). - Work Locally: Add your files and run
hugo serverlocally to ensure everything renders correctly. - Commit: If you are satisfied, stage and commit your changes to your branch.
- Pull Request: Open a Pull Request (PR) against the
mainbranch.
A custom GitHub Action workflow is configured to build the Hugo site automatically. Once your PR has been merged, it will push the live site to GitHub Pages.
Our site uses the Blowfish theme, which provides powerful built-in tools to make content look great without writing complex HTML.
- Shortcodes: These are simple snippets you can use directly inside your
index.mdfiles to create complex layouts. For example, you can use shortcodes to easily insert image carousels, interactive buttons, formatted timelines, or accordions directly into your text. - Partials: These are structural HTML templates used to build the overall architecture of the site (like the header, footer, or article layouts). You generally won't need to touch these for standard content editing, but they are useful to know about if you need to deeply customize the theme's core code.