GCAIF Website

Static site for the Goizueta Center for AI in Finance (GCAIF). Plain HTML/CSS, no build step, deployed via GitHub Pages.

Structure

website/
  index.html          Home page
  people.html          Leadership, faculty advisory committee, admin, external advisors
  programs.html        Seminar series, research/educational grants, travel grants
  get-involved.html    Mailing list, birthday social, conference, partnerships
  css/style.css        Shared styles (all pages link to this one file)
  .nojekyll             Tells GitHub Pages to skip Jekyll processing

Design sourcing

Colors, typography treatment, and layout patterns were pulled from Goizueta's public brand materials so this site reads as a Goizueta property rather than a generic template:

• Colors — exact hex values from the official brand guide (goizueta.emory.edu/brand/web-guide.pdf) and living style guide (goizueta_theme/dist/style-guide/item-general-colors.html): Emory Blue #002F6C, WaterHub Blue #0033A0, Eagle Blue #0C2340, Emory Yellow #F2A900, plus the Dogwood White / blue-tint neutrals used for section backgrounds.
• Fonts — the official brand fonts are Resolve Sans (display/headline sans) and Goudy Old Style (serif accent, used in the Emory wordmark and for editorial contrast). Both are commercial fonts we don't have license files for, so this site substitutes free, similarly-shaped Google Fonts: Archivo (wide weight range, works well in the brand's "all-caps headline" style) and EB Garamond (an old-style serif that plays the same contrast role Goudy Old Style does in official materials). If Goizueta Marketing can provide the licensed font files, swap the @import and font-family values in css/style.css.
• Layout patterns — the header lockup (parent logo + section wordmark), page-header banners, faculty photo-grid cards, and footer structure (address / contact / sub-footer with copyright) echo the pattern used on goizueta.emory.edu/faculty/business-society, one of Goizueta's other center sites.
• The wave — the thin curved divider under each page header is a simple, restrained nod to "the wave," a recurring connective graphic in Goizueta's brand system (see the brand guide, p.17).

Before you publish

• Logo: the header currently hotlinks Goizueta's live logo (https://goizueta.emory.edu/themes/custom/goizueta_theme/logo.svg). This keeps it automatically in sync with the official mark, but it's a soft dependency on Emory's server. For a more resilient setup, download the approved logo file from emory.biz/brand (per the brand guide), add it to an assets/ folder here, and point the <img class="parent-logo"> src at the local copy instead.
• Replace the placeholder email gcaif@emory.edu in every page's footer and mailto links with the Center's real contact address.
• Replace the "Photo" placeholders on the People page with real headshots (add image files to an assets/ folder and update the <img> tags).
• Update seminar/program details as new announcements go out (call for proposals, travel grant program, birthday party date, etc.).

Publish to GitHub Pages

1. Create a new (empty) repository on GitHub, e.g. gcaif-website. Do not initialize it with a README, license, or .gitignore — this folder already has content.

2. From this folder, initialize git and push:

   cd ~/GCAIF/website
   git init
   git add .
   git commit -m "Initial GCAIF website"
   git branch -M main
   git remote add origin https://github.com/<your-username>/gcaif-website.git
   git push -u origin main

3. On GitHub, go to the repo's Settings → Pages. Under "Build and deployment," set Source to "Deploy from a branch," branch main, folder / (root). Save.

4. GitHub will publish the site at:

   https://<your-username>.github.io/gcaif-website/
   

   (First deploy can take a minute or two.)

5. Optional: to use a custom domain (e.g. gcaif.emory.edu), add a CNAME file to this folder containing just the domain name, and configure a DNS CNAME record pointing to <your-username>.github.io. Emory's IT/domain team will likely need to be involved for an emory.edu subdomain.

Making future edits

Come back to this conversation (or a new one) and describe the change you want — new speaker, updated grant amounts, a news item, real headshots, etc. I'll edit the files directly in this folder; you then just re-run:

git add .
git commit -m "Update site"
git push

GitHub Pages redeploys automatically within a minute or two of each push.