Repository navigation
Overhaul - #15
Merged
Merged
Overhaul#15
Conversation
Small rounded-square member photos under each news item's date and before lab members' names in publication author lists. group.html and publications.html act as the member/paper database, read at runtime by js/people.js, so nothing extra needs to be kept in sync. Faces link to the member's own site, or to their card on group.html.
News, publications, members, gallery and research topics now live in data/<db>/ as markdown/YAML entries with a config.toml each; pages are Jinja templates rendered into _site/. Gallery thumbnails are generated at build time. Built pages match the previous pages element for element.
Head, header/nav, footer and drawer markup live once in base.html, with nav, footer logos and lab name in data/site.toml. The CSS shared by all pages is in templates/partials/, included at the same cascade positions the pages always had them. Built pages render pixel-identically.
…a/ layout - data/<db>/README.md: how to add an entry, field reference, config.toml settings - .github/workflows/deploy.yml: build with tools/build.py, deploy to Pages - pre-commit hook: validate data/, optimize images in their new directories; hook and optimizer now run on macOS bash 3.2 - remove tools/sync-home-news.py and _archive/ (pre-2026 news is in data/news) - README.md / CLAUDE.md describe the new layout
…red at build time - data/publications/papers.bib replaces the per-year YAML files: headings come from year / is_preprint / is_previous, highlights from oral / spotlight / award / also; any other field is a link - members.yaml gives every person a tag; news text and BibTeX authors refer to lab people only as @tag, and news names papers by BibTeX key - member faces are rendered by tools/build.py from tags and paper keys, not guessed in the browser; js/people.js and the home page's runtime news refresh are removed - blank lines between entries in members/gallery/topics YAML
The build fills in the entry's paper URL, and a linked paper counts for faces, so front matter paper: is only needed for papers without a link.
…plates atop every data file data/news/<year>.yaml replaces the per-item markdown files; items carry idx, date, text and optional paper, with a blank line between them. Every data file (news, members, gallery, topics, papers.bib) now opens with a comment listing all fields of an entry. Built pages are unchanged.
…r), paper: "@lee26fresco"
A key repeated within one YAML file is now an error rather than silently dropping the earlier entry.
…n static/research_focus Research topics change rarely and are prose, like hiring, so they live in the page again instead of data/research/. Built pages are unchanged.
research, hiring and contact are plain HTML in content/ (what goes inside <main>). layout/page.html inserts them into the shared frame; their CSS is layout/styles/<page>.css, the drawer script is shared in layout/scripts/. Rules keep their cascade (checked: no page rule overlaps the footer CSS it now follows). Built pages render the same.
Remove the indent left over from the old pages, add a heading comment per research topic, and break long paper-tag lines at existing spaces. Built pages are pixel-identical.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.