This Website is based on https://academicpages.github.io/.
The site uses one custom Jekyll layout and a small set of partials; the AcademicPages templates it was forked from have been removed.
_layouts/academic.html– page shell (header, content column, footer, back-to-top)._includes/academic-*.html– header, contact row, news list, publication entry, publication toolbar, share-card metadata._sass/_academic.scss– all styles (ink-blue tokens, light and dark themes).assets/js/academic.js– theme toggle, news toggle, back-to-top. Everything degrades to fully visible content without JS._pages/about.md,_pages/publications.md,_pages/awards.md– page content.
Content lives in data files:
_data/publications.yml– one entry per paper:id,title,authors,year,kind(publicationorpreprint),venue,venue_full, optionalnote,links(pills:paper,arxiv,code,slides,video).- Venue pills: the first link of a peer-reviewed paper (
kind: paper) is labelled by the page it opens:Proceedings(PMLR, ICLR proceedings, ACM Digital Library),Journal(journal pages), orOpenReview. The build check enforces this. When PMLR publishes ICML 2026, point the three ICML 2026 papers to PMLR, relabel themProceedings, and update the PowerFlow and Heavy-Tailed MDPs links in the Research Overview, which must equal each paper's first link. _data/news.yml– homepage news (when, Markdowntext), newest first. The news section is currently hidden; re-enable it by restoring the include line noted in_pages/about.md._data/navigation.yml– header links.
Local preview (this machine needs the Homebrew Ruby, not the system one):
export PATH="/opt/homebrew/opt/ruby/bin:/opt/homebrew/lib/ruby/gems/4.0.0/bin:$PATH"
bundle exec jekyll serve --host 127.0.0.1 --port 4000
jekyll build keeps the production url, so a static preview of the build output
needs a config override such as --config _config.yml,local.yml with
url: "http://127.0.0.1:4000"; jekyll serve handles this automatically.
Every Jekyll build writes its UTC Unix timestamp to version.json, the page's
site-build-version metadata, and the URLs of local stylesheets, scripts, avatars
and icons. No manual version increment or additional Jekyll plugin is needed.
The inline _includes/check-update.js checks version.json on each page load and
when a page is restored from the browser's back/forward cache. Requests use
cache: "no-store" and a unique query parameter. A newer build triggers one
navigation to a fresh URL for the same page; existing query parameters and anchors
are preserved, and the internal update parameter is then removed. Older manifests,
failed requests and incomplete deployments do not cause repeated reloads.
This is a client-side update check, not a change to GitHub Pages' HTTP cache headers. It requires JavaScript and a network connection and may briefly display the cached page before an update arrives. Existing cached pages from before this feature was deployed must first expire or be refreshed once to acquire it.
Run npm test for update-check regression tests (Node.js 18 or later; no npm
dependencies are needed). After bundle exec jekyll build, run
bundle exec ruby tests/check-build.rb _site to verify generated version metadata
and asset URLs.