Today's lesson

Get your portfolio live

By the end of class your site exists, both pages are on it, and they link to each other. If you missed a week, everything you need is on this page — start at the block you're behind on.

1 Where we are

What you can already do

Four sessions in. Here is what you have been building.

Week 1 · Sep 2

The question

You wrote down why you think frequent mental distress is higher in Jamaica than in most of New York City.

Week 2 · Sep 9

Who actually answered

Every health statistic is the surviving end of a pipeline, and the people who fall out of it are not random. You learned to look for the sampling frame — the list people were drawn from — and the response rate, the share who actually answered. Lakeview's was 28 percent.

Week 3 · Sep 16

What is in a dataset

Nominal, ordinal, interval, ratio. You can look at a column and say what you are allowed to do with it — and catch an average that should never have been published.

Week 4 · Sep 23

What a study can claim

Cross-sectional, cohort, case-control, randomized trial. You can name a design from how and when it measured, and say whether the authors went further than their study allowed.

Today

Publish it

Week 4 is the first piece of work worth showing someone. Today it goes online under your name, where an employer could read it.

Three questions you now own

Who is missing from this number? What kind of thing is in this column? And does this study allow the sentence they wrote?

2 Why this is in a biostatistics course

Somebody has to be able to check your work

The term

Reproducibility

Someone else takes your data and your steps, runs them, and gets the same numbers you published.

Why it is the minimum standard

Think about the green space study from last week. Nine thousand eight hundred people, eight years of follow-up. Nobody is running that again to check it — not for the money, not for the time.

So when a study cannot be repeated, the only check left is whether someone can take what you had and arrive where you arrived.

This is a real rule, not a nice idea

In 2009 the journal Biostatistics — a serious one in this field — set up a system where authors submit the data and the code behind an accepted paper, and an editor can run that code and confirm it produces the published results.

A journal decided that "trust us" was not good enough. Show the file, show the steps.

Peng, R. D. (2009). Reproducible research and Biostatistics. Biostatistics, 10(3), 405–408.
doi.org/10.1093/biostatistics/kxp014

Which is why agencies publish this way

Through the pandemic, the New York City Health Department published the city's COVID numbers to a GitHub repository, updated continuously from March 2020 until October 2025. That is where reporters, researchers and other agencies got the figures they published. It was archived this past May and replaced by a new one for respiratory illness data. The same department keeps another repository for the maps that appear on its own web pages — the files in the cabinet are what the public site is built from.

So

Finding the data file, reading the notes, seeing what changed and when — that is a public health skill, not a web skill.

And the reason that is yours

A public health employer wants evidence you can look at a published claim and say what is wrong with it. A link shows that in thirty seconds. A transcript does not.

3 The three tools

Three jobs, three tools

People lump these together and then get lost. They do completely different things.

Tool 1

Copilot

The writer

GitHub's AI assistant, built by GitHub and Microsoft. It is an interface wrapped around a large language model that someone else trained.

You tell it what you want. It writes the file.

It does not store anything and it does not put anything on the internet. Close the window and the work is gone unless you saved it somewhere.

Tool 2

GitHub

The filing cabinet

A hosting service for code and data, built on version-control software called git. Started in 2008, bought by Microsoft in 2018.

Your files live here, and every version of them. Nothing here is a website yet — it is a drawer with documents in it.

Every time you save, it writes down what changed and when. That history is the receipt.

Tool 3

Vercel

The printer

A hosting platform. It watches a repository and serves what is in it to a web address, handling the server and the security certificate. It also stores secret keys, which is how a real application uses a password without writing it into a file everyone can read.

It watches your filing cabinet. Whatever is in there, it publishes to the internet at your web address.

Change a file, and about a minute later the live site shows the change. You never touch Vercel again after setup.

you write it → Copilot  ·  you keep it → GitHub  ·  the world sees it → Vercel

Why this matters beyond today

The filing cabinet keeps every version, dated. Anyone can see how a page got to be what it is — the same reason a notebook beats a spreadsheet.

4 Catching up

The two pages you should have

If you have both, skip to section 3. If you are missing one, do it now — everything is here.

Page 1 — your homepage

index.html  ·  from Week 3

What it is

Who you are, what you care about in public health, and a portfolio section that grows each week.

What it should have on it

  • Your name and a one-sentence description of yourself
  • A circle with your initials where a photo can go later
  • About me — why public health, the issue you care about, where you are headed
  • Skills
  • A PH 320 Portfolio section with cards for Weeks 3, 4 and 5 that say "Coming soon"
  • Your school email, and LinkedIn if you have one

The questions Copilot will ask you

  1. What name do you want shown?
  2. Your major, and when you expect to graduate
  3. One sentence describing yourself
  4. Why you chose public health
  5. A health issue you care about, and why
  6. The career you are working toward
  7. Three skills or strengths
  8. The email you want shown
  9. LinkedIn, if you want it
  10. Colors you like, if you have a preference

The prompt — paste this into Copilot

Prompt 1 · builds your homepage
You are helping me, a public health student, build my personal portfolio homepage for GitHub Pages. I don't know how to code, so you'll do all the code.

HOW TO WORK WITH ME
- Interview me first. Ask ONE question at a time and wait for my answer before asking the next one.
- Keep your questions short and friendly. If my answer is very short, you may ask one follow-up to get a little more.
- Do not write any code until I've answered every question.
- Before you write the code, show me a short summary of my answers and ask "Anything to change?" Only write the code after I say it looks good.

ASK ME THESE QUESTIONS, IN THIS ORDER
1. What name do you want shown on your page?
2. What's your major, and when do you expect to graduate?
3. In one sentence, how would you describe yourself? (Example: "Public health student focused on community mental health.")
4. Why did you choose public health?
5. What health issue do you care most about, and why?
6. What career or job are you working toward?
7. What are three skills or strengths you have?
8. What email do you want shown? (School email is fine.)
9. Do you have a LinkedIn link you want to include? (Optional.)
10. Any colors you like? (Optional.)

WHEN YOU WRITE THE CODE
- Give me ONE complete file called index.html, in a single code block, from <!DOCTYPE html> to </html>. Put all the styling inside the same file. No other files, nothing to install. Do not skip or shorten anything.
- Clean, professional, easy to read, and it must look good on a phone and a laptop.
- Use ONLY what I told you. Do not invent awards, jobs, certifications, numbers, or experience.
- Never include a phone number, home address, or student ID.
- After the code block, stop. Do not add instructions or next steps.

THE PAGE MUST HAVE
1. A hero section at the top with my name, my one-sentence description, and a photo spot.
   - Photo spot: show a circle with my initials. Right above it, put a clear HTML comment that says exactly which line to change to show my photo instead, using the file name photo.jpg.
2. An "About me" section using my answers about why I chose public health, the issue I care about, and my career goal.
3. A "Skills" section.
4. A section titled "PH 320 Portfolio — Applied Biostatistics in Public Health, York College CUNY" with cards for Week 3, Week 4, and Week 5. Each card says "Coming soon." Put an HTML comment above each card showing me where to add a link later.
5. A contact section with only my email and LinkedIn (if I gave one).

Start now by asking me question 1.

Save what it gives you as index.html.

Page 2 — your first piece

cross-sectional.html  ·  from Week 4

What it is

About 250 words taking one cross-sectional study apart — Study A from the Week 4 opener, or Study G from the workshop.

How it is built

  1. Open with the claim the researchers made
  2. Say what they actually did — who they measured, and when
  3. Name the gap: what the claim assumed that the study never established
  4. Generalize: what cross-sectional data can and cannot support
  5. Close with the sentence they should have published instead

You write the words yourself first. Copilot only turns them into a page. It may fix spelling and grammar; it may not think for you.

The prompt — paste this, then paste your finished writing underneath it

Prompt 2 · turns your writing into a page
I have written a short analytical piece for my public portfolio site. Build the page for me. I do not write code.

Give me exactly two things, clearly labeled, and nothing else:

THING 1 - the file. Start by writing the line:
  "Save this as: cross-sectional.html"
Then give me one complete HTML file in a single code block, from
<!DOCTYPE html> to </html>. Do not shorten it or leave anything out.

THING 2 - the link. Give me one line of HTML, in its own code block,
that I can paste into my homepage so people can reach this page:
  <a href="cross-sectional.html">MY TITLE HERE</a>
with my real title filled in.

Rules for the file:
- Fix my spelling, grammar and punctuation, and split a run-on
  sentence if you need to. That is the only editing you may do.
- Keep my wording and my ideas. Do not rewrite sentences to sound
  better, do not add or remove points, do not add an introduction or
  a conclusion, and do not invent a new title.
- At the very end, after everything else, list any sentence you
  changed by more than a word or two, so I can check it.
- One <h1> with my title, then my paragraphs exactly as I wrote them.
- Clean, readable typography. Generous line height. A single column
  no wider than about 700px, centered. It must read well on a phone.
- All CSS inside a <style> tag in the same file. No external files,
  no frameworks, no JavaScript.
- At the bottom, in small text: my name and
  "PH 320 · Applied Biostatistics in Public Health".
- Add a link at the bottom back to my homepage: <a href="index.html">Home</a>

Do not explain anything. Do not give me instructions. Just the two
things above.

Here is my piece:

Save what it gives you as cross-sectional.html. Lowercase, no spaces.

5 Your cabinet

What you are looking at in GitHub

Open your repository and you see a list of files. Here is what each one is.

index.html
Your homepage. The only file whose name nobody has to type — the web address on its own shows this page.
cross-sectional.html
Your Week 4 piece. A room in the house. Reached by adding its name to your address.
photo.jpg
Your picture, if you uploaded one. The name has to match what the page asks for, exactly.
README.md
A note about the project. GitHub shows it to anyone browsing your files. It never appears on your website.
.gitignore
A list of files GitHub is told not to store — junk, and anything secret.
.DS_Store
Litter the Mac Finder leaves behind. Harmless. Delete it if you see it.
favicon.ico
The tiny icon in the browser tab.
styles.css
Styling, if the AI split it into its own file instead of keeping it inside the page.
vercel.json
Settings for the hosting platform. You only have one if something created it for you.
package.json
node_modules
Signs your project started from a template rather than a plain file. If a node_modules folder is sitting in your repository, something went sideways — ask.
main
The name of your one version of the project. You will not need any other.
Commits
Not a file — the list down the side. Every save you have ever made, with the date. This is your history, and nothing is ever really lost.

If you did not make a file, and the site works, leave it alone. That is a real rule, not a dodge — professionals use it every day.

Commit means save. There is no separate "publish" button. You commit, Vercel notices, and about a minute later the live page has changed.

Uploading a photo

Add file → Upload files, drag the picture in, commit. Two things that break it: the name must be exactly what the HTML asks for, and iPhone photos are often .HEIC files, which browsers will not display. Save it as a JPEG first. If that is a fight, keep your initials circle today and do the photo later.

6 Reading it

Three lines of HTML

You will not write this. You should be able to read it, the same way you read a line of Python.

<h1>Erin Jacques</h1>
<p>Public health student focused on community mental health.</p>
<a href="cross-sectional.html">Read my analysis</a>

<h1>A heading. The tag wraps around the text, and the closing tag has a slash: </h1>. Everything works that way.
<p>A paragraph. Ordinary text.
<a href>A link. The words between the tags are what people see and click. href is where the click goes, and nobody sees it.

HTML stands for HyperText Markup Language. It is plain text with tags that say what each piece is — a heading, a paragraph, a link. "Hypertext" is just the old word for text with links in it.

The one to remember

href is the only thing that decides where a click lands. When a link is broken, that is where you look.

7 Your address

What the URL actually is

Vercel gives you one address. That address is your homepage. Every other page is that address, a slash, and the file name.

If Vercel gave you erin-portfolio.vercel.app erin-portfolio.vercel.app → index.html
erin-portfolio.vercel.app/cross-sectional.html → cross-sectional.html

Vercel only ever shows you the first one, which is why your second page feels missing. It is there. Nothing points at it yet.

If you type the address and get a 404, the file name does not match: a capital letter, a space, or a missing .html. Lowercase, no spaces, every time.

8 Today's work

Connect the two pages

Right now you have two pages and no way to walk between them. A site is pages that link to each other. That is the only thing missing.

This prompt is different from the other two. You are not asking for a new page — you are handing Copilot a file you already have and asking for it back, changed. It must return the whole file, or you will paste a fragment and break your page.

Open index.html in GitHub, click the pencil to edit, select everything, and copy it. Then:

Prompt 3 · links your pages together
I have a portfolio website made of two pages that do not link to each
other yet. I do not write code. Fix that for me.

Below I am pasting my current index.html, exactly as it is now.

Give me back the COMPLETE updated file, from <!DOCTYPE html> to
</html>, in one code block. Do not give me a snippet or a
"replace this part" instruction — I need the whole file to paste over
the old one.

Make exactly these three changes and nothing else:

1. Add a navigation row at the very top of the page, above everything,
   with two links:
      Home → index.html
      My title below → cross-sectional.html
   Style it to match the page. Keep it simple, one line of text links.

2. Find the portfolio card for Week 4 that says "Coming soon" and turn
   it into a working link to cross-sectional.html, using my title.

3. Under my name at the top, add this line in smaller text:
   "PH 320: Why is frequent mental distress higher in Jamaica than in
   most of New York City - and how would we know that's really true?"

Do not restyle the page, do not rewrite my words, do not add sections,
do not remove anything.

After the full file, give me the navigation row on its own, in a second
code block, so I can paste the same one into cross-sectional.html.

My title for the Week 4 piece is: [TYPE YOUR TITLE HERE]

Here is my index.html:

Paste your whole index.html underneath the prompt. Copilot returns the full updated file and a navigation row.

  1. Replace your homepage

    In GitHub, edit index.html, select all, delete, paste the new version, commit.

  2. Add the same navigation to your other page

    Edit cross-sectional.html, paste the navigation row just after <body>, commit.

  3. Wait a minute, then open your site

    Click from the homepage to your piece, and from the piece back home. If both work, you are done.

9 Before you leave

What your site should look like

  • Typing your Vercel address shows your homepage
  • Your name, your one-sentence description, and the course question are at the top
  • The Week 4 card is a link, not "Coming soon"
  • Clicking it opens your piece
  • Your piece has a link back to Home, and it works
  • You have handed in your address

Your analysis is not finished when you understand it. It is finished when someone else can find it, read it, and check it.