AI for Research Efficiency, episode 6: Publish a page with Vercel
Narration: an AI-generated voice (ElevenLabs).

[0:00] A link, not attachments
Sharing results the usual way: an email with six attachments, and a hope that everyone opens the right one.
Or one link: a page with the findings, where every claim links to its source.
AI for Research Efficiency. Episode 6: Publish a page with Vercel.
Last time, your folder got a history with Git, and a private copy on GitHub.
This time: turn your results into a page, publish it to a link, and know who can see it, and on what terms.

[0:40] 1. The agent makes the page
One: ask the agent for the page.
In the practice folder, ask for one page from the review's findings, with every claim linked to its source.
It wrote a small script that builds the page, then checked the links: 344, all from the review's own list of sources.

[1:04] 2. Look before you publish
Two: look at it on your own computer first.
Type start, then the file's name, and it opens in your browser. On a Mac, type open.
Click a few links: each figure should land on its paper.

[1:24] 3. Commit and push
Three: commit it, and push.
The agent put its commit on a branch of its own, and offered to merge it into main.
That matters here, because main becomes the published page. So merge it, and push, as in episode 5.

[1:43] 4. Import it in Vercel
Four: publish it, with nothing to install.
In Vercel, choose New Project, connect your GitHub account, and import the repository.
It finds no framework, so it serves the folder as it is. Press Deploy.
When it says Ready, your page has its address.
If the repository isn't in the list, Vercel's GitHub app can only see the repositories you chose. Choose Configure GitHub App, and add it.

[2:19] 5. Change it, and push
Five: change it, and push.
Every push to main updates the page by itself. A push to any other branch gets a preview address of its own.
So the agent added a date on a new branch: check the preview, then merge it, and the page updates.

[2:40] 6. Two settings to check
Six: two settings to check on the free plan.
Who can see it: Standard Protection asks visitors to previews to sign in with Vercel, and leaves the main address open. The free plan has no passwords.
And your content: on the free Hobby plan, Vercel may use it to train AI models, unless you switch that off, under Team Settings, Data Preferences.

[3:09] 7. The terms, said plainly
Seven: the terms, said plainly.
Hobby is for personal or non-commercial use, and Vercel counts a paid employee writing the code as commercial.
So a lab's or a department's site may need Pro, at $20 a month, or another host.
Pro is a paid plan, and the one this series' presenter uses for many projects.
Free hosts without that clause include GitHub Pages, Netlify and Cloudflare Pages.
Wherever you publish, put up only what you'd show anyone: no unpublished results, nothing that isn't yours, and no health information.

[3:52] Try it
Pause here, and try it: ask your agent for a page from your practice folder's findings, and open it in your browser.

[4:04] Review and next
So: a link, not attachments. Look before you publish, and check who can see it, and on what terms.
Next: tokens and limits.