Update site for NIAID BRC AI Codeathon 2.0 (Sept 16-18, 2026)#4
Open
dannon wants to merge 9 commits into
Open
Conversation
…ID BRC AI Codeathon 2.0 (September 16-18, 2026), pull in the new two-focus-area framing (Literature RAG/LLM + MCP/agentic workflow automation) and goals from the announcement doc, and replace the schedule with the new Argonne agenda. Kept the 2025 project pages around -- relabeled the nav as "Past Projects" and added a banner on the listing pointing back to the 2026 announcement so visitors aren't confused about which event the projects belong to. Application form link is still a placeholder since the form isn't ready yet; deadline shown as August 15, 2026.
…g template look into an editorial-scientific direction. Swapped in Fraunces (display) + IBM Plex Sans/Mono via Google Fonts, dropped the local Atkinson, and rebuilt the palette around a warm paper background with ink text and rust + teal accents. Rewrote the homepage, schedule, projects listing, and project detail layout to match -- asymmetric hero, numbered focus areas, big day numerals on the schedule with tag pills, and a hairline 2-col archive grid. Header/footer redone in the same vocabulary. Italic display weights show up a lot right now which we'll probably want to tune down in a follow-up.
… drop to 200/300 with tighter letter-spacing so the big numerals (01/02 focus areas, 16/17/18 day numerals, hero "2.0") still feel deliberate without leaning on italic serif. Also moved those large numerals off Plex Mono onto Plex Sans -- Plex Mono's default zero is the centered-dot glyph and there's no OpenType feature to plain it out, so it kept showing up where we didn't want it. Mono stays for small labels, eyebrows, and schedule times where the dotted zero reads as intentional. Same paper/ink/rust/teal palette, same editorial structure, just sans throughout.
…omponent (circle-with-dot motif -- reclaims the dotted-zero glyph we'd rejected from Plex Mono and uses it as a designed signature) and put it in section eyebrows, page-head eyebrows, the hero meta row, and a couple of section-divider blocks on the homepage. Dropped the big display weights another notch (200 -> 100) with tighter letter-spacing, and added rust hairlines under "2.0" in the hero plus under each day numeral on the schedule. While in here: replaced the Astro-template favicon with a small rust circle-and-dot mark on ink, and generated a proper 1200x630 Open Graph card (scripts/og-template.svg + scripts/render-og.mjs using sharp to render PNG). BaseHead now points og:image at the new card with explicit width/height, and the now-unused FallbackImage import is gone. Small contrast bumps on the lowest-opacity footer text so the tiny copyright and labels comfortably pass AA against the dark background. Header tried a Mark next to the brand briefly -- pulled it back out, the brand reads cleaner as a plain two-line stack and the mark works better with breathing room in the eyebrows below.
# Conflicts: # src/components/Header.astro # src/layouts/ProjectPost.astro
…" are now two block-level spans inside the h1 with white-space: nowrap, instead of relying on flow wrapping. Also dropped the rust hairline under "2.0" -- with the new layout it was reading as a strikethrough through the digits rather than an underline below them, and the rust color is doing enough accent work on its own.
…the three-BRC collaboration -- BV-BRC, BRC Analytics, and Pathogen Data Network -- gets dedicated, prominent treatment instead of being buried in the eyebrow and intro paragraph. Reuses the numbered manifesto layout from focus areas (01/02/03) but in teal so it reads as context ("who") rather than action ("what"). Pulled the descriptions from the report page so the framing is consistent across the site.
Also fixed the brc-analytics.org and pathogendatanetwork.org URLs to drop the www. subdomain (those domains don't resolve with www) -- kept www.bv-brc.org since that one does. Same fixes applied in the report page where those URLs were originally imported from main.
Added .pr-shots/ and pnpm-lock.yaml to .gitignore so local screenshot staging and stray pnpm runs don't keep showing up as untracked.
Plus a prettier pass on the project markdown files -- mechanical table-realignment noise after schema/content updates, no semantic changes.
…t sits in the gap between baseline and the weekday label instead of cutting through the bottom curves of 6/7/8. Same fix we made on the hero "2.0" -- with line-height: 0.85 the box bottom lands right at the digit baseline, so a small positive value reads as a strikethrough.
dannon
force-pushed
the
update-for-codeathon-2-0
branch
from
0a12317 to
b9a7ee8
Compare
…"Travel and lodging support may be available for a limited number of participants." Slotted into the existing apply paragraph between the "free but limited" framing and the "more details soon" tail.
dannon
force-pushed
the
update-for-codeathon-2-0
branch
from
b9a7ee8 to
2282c34
Compare
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
1 participant
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.
Summary
Three rounds of changes on this PR, against the planning docs for NIAID BRC AI Codeathon 2.0:
/reportpage,videofield on the project schema, and various 2025 project updates that landed on main while this was in flightHomepage
Editorial hero with the two focus areas as numbered manifesto sections, "Apply" CTA in ink with rust accents.
Schedule
Big day numerals (16 / 17 / 18) with rust hairlines, sticky day rail with each day's theme, color-coded tag pills (Keynote, Tour, Build, Reports, Finale).
Past Projects
2025 archive relabeled with a banner pointing back to the 2026 announcement. Stat strip (14 projects / 3 days / ANL) above a hairline-divided grid.
2025 Report
The
/reportpage that came in from main, restyled to match the new vocabulary -- editorial drop cap, full-width group photo with caption, project recap, YouTube link callout.Mobile
Responsive stack -- hero meta drops below title, focus areas single-column, schedule day rail stops sticking.
Open Graph card
What link previews show in Slack / Twitter / email.
Open items
Test plan
npm run buildsucceeds on the mergenpm run dev