The public website for Computational Biology at Berkeley, built with Vite, React, TypeScript, shadcn/ui, and Tailwind CSS.
Use Node.js 20.19+ or 22.12+ (including newer supported releases).
npm ci
npm test
npm run devRun npm run build for the same credential-free production build used by GitHub Pages. The build validates officer data before compiling the site.
Builds copy public assets with a filter that excludes the local public/fetched/
cache. The build validator rejects any release artifact that contains this cache.
Tracked officer portraits and archive snapshots remain included.
The package overrides select patched postcss-selector-parser and minimatch
versions for the typography and TypeScript ESLint tools. Keep these overrides
until the upstream packages require patched versions themselves.
Fall 2026 deliberately separates approved roster decisions from submitted public profile content:
src/data/officersFa26Roster.jsonowns cohort membership, roles, order, stable IDs, and reviewed fallback public content, including submissions received outside Notion.src/data/officerProfilesFa26.jsonis a reviewed, public-only snapshot of in-window officer form responses.scripts/lib/officer-profile-cohorts.jsowns operational file paths and the explicit intake window; upstream database identifiers stay in protected environment secrets and out of the client bundle.src/data/compileOfficerDirectory.jsmatches responses to the roster, keeps the newest nonblank public fields, normalizes links, and ignores unmatched people.public/officers/fa26/stores stable headshot assets.public/officers/archive/stores immutable Fall 2025 and Spring 2026 snapshots so historical tabs work in a clean checkout.
Notion is private intake, not a publishing system. Maintainers use the controlled
officers:notion:dry-run, officers:notion:check, and
officers:notion:write commands described in scripts/README.md to prepare a
sanitized working-tree change. The write command does not commit, push,
deploy, or write anything back to Notion. A human must review the Git diff and
the staging site before promotion.
Each profile record in the public snapshot is limited to provenance ID, submission time, full and preferred names, headshot path, bio, personal website, LinkedIn, GitHub, and ORCID. Never copy email, phone number, birthday, scheduling data, another private form field, or an upstream database identifier into the snapshot or roster. A manually reviewed submission received outside Notion may populate only those same publishable content fields on the matching approved roster entry; it must not use a fabricated Notion provenance ID. Run:
npm test
npm run validate:officersThe validator reports unmatched responses, invalid public links, missing assets, and officers still waiting for a current profile response. See scripts/README.md for the update workflow and .agents/skills/pre-production-checklist/SKILL.md before a production promotion.
src/data/siteIdentity.jsonandsrc/data/sitePages.jsonare the shared registries for the public identity, indexable routes, page titles, and descriptions.src/data/siteIdentity.jsonalso stores the public Google Search Console verification token that the build emits as a metadata tag.npm run buildcreates rendered HTML at each route directory, then generates and validatesdist/sitemap.xmlanddist/robots.txt.src/components/RouteMetadata.tsxkeeps metadata synchronized during client-side navigation.- Production builds are indexable by default. Staging sets
VITE_NOINDEX=trueand a stagingVITE_SITE_ORIGIN, which marks every pagenoindex, nofollowand suppresses the sitemap. Its robots file allows fetching so crawlers can observe the page-level directive. public/404.htmlis alwaysnoindex; internal/conceptsreview routes are intentionally absent from the sitemap and static route output.
src/data/notices.json is the reviewed source of public event notices. Use stable
IDs, verified HTTPS links, and explicit timezone offsets on both startsAt and
endsAt. Do not add private Slack discussions or contact information. Run
npm run notices:sync after edits to update the managed notices section of
public/llms.txt.
The home page displays dismissible banners and event cards; the calendar displays the same cards. A dismissal lasts for the current browser tab and resets when the notice content changes. Open pages hide notices at the event end time.
npm run build freezes one active-notice snapshot for the client, server-rendered
HTML, dist/notices.json, and the current-notices section in dist/llms.txt.
Expired notice records can remain in the source as history; they never enter a
new build. SITE_NOTICES_NOW supplies an explicit test clock for expiry checks.
The production Pages workflow runs an expiration check every hour at minute 10. It compares the published snapshot with the active source records and deploys only when they differ. The November 16 study session ends at 10 p.m. PST; its first scheduled cleanup is November 17 at 06:10 UTC (10:10 p.m. PST). GitHub may delay scheduled runs. The browser expiry check does not depend on the scheduler. The job uses read-only source permissions and the existing Pages deployment; it does not edit or push source files. Pushes and manual runs still deploy normally.
The user-authorized Codex automation checks the CompBio Slack workspace on
Wednesday, Friday, and Sunday at 9 a.m. Pacific. Review #general and
#publicity-requests-2026, including corrections in their threads. Publish only
facts intended for public promotion. Validate, deploy and verify staging before
promoting the same commit to production; preserve unrelated local work.
- Pushes to
devdeploy the staging GitHub Pages site from theHilo-Hilostaging repository. - Pushes to
maindeploy production fromCompbioAtBerkeley/compbioatberkeley.github.io.
Before every staging or production deployment, review changed public facts,
links, route descriptions, and capability claims against public/llms.txt.
Update llms.txt in the same change whenever it indexes or summarizes the
affected information. Review public/agent-instructions.md and
public/developers.md at the same time when source-selection guidance or
technical capabilities change. npm test and npm run build enforce the
machine-readable facts that can be checked automatically; after deployment,
verify the live /llms.txt from the same commit as the HTML site.
Neither build reads Notion or Google Sheets credentials. Form intake is reviewed and versioned before publication, so the same commit produces the same site in local, staging, and production environments. The separate weekly/manual drift workflow may read Notion with a read-only integration, but it cannot modify repository contents or publish candidate data.
/newsletter/lists editions by academic term and issue number, newest first. Add edition metadata tosrc/data/newsletters.ts. Do not infer a publication date from PDF metadata.- The first edition is
/newsletter/fall-2026-newsletter-1/. Its text and embedded link targets were extracted from the supplied nine-page Fall 2026 draft intosrc/data/newsletters/fall-2026-newsletter-1.json. Column text was restored to reading order. - The reader uses a web editorial layout with the site’s blue and gold palette, responsive typography, a sticky section guide, reading progress, expandable project descriptions, and photo dialogs. The PDF supplies the content, photos, and captions, rather than page geometry. It contains no embedded PDF or whole-page image substitutes. Preview slides are HTML too.
- Event photos are extracted WebP assets in
public/newsletters/fall-2026-newsletter-1/. Project logos reusesrc/data/partners.tsand the existing collabs assets. Google DeepVariant uses the collabs Google wordmark. Progenic’s existing asset is 119 by 200 pixels; it is displayed at a bounded size. - Add each new reader route to
src/data/sitePages.jsonso the static build produces direct-link HTML and route metadata. Updatepublic/llms.txtwith the edition and its academic term. /developers/has been removed. The separate machine-readable developer index remains at/developers.md.