Next steps

Your site is live, and it's yours. Here is how to keep building on it.

Keep building your site A fresh chat, the Role's prompt, as today; this page shows how, from adding your own content to editing it.
Start a new site with web-factory The open-source factory from the closing slide, for building your next site at home. Get started with web-factory shows the two ways in and Kickoff, Where to start at home the first commands, and The web factory explains every station. The code is on GitHub: fabkrum/web-factory.
Go deeper The deep dives explain what was behind every step today: web development, AI, the building blocks and agentic frameworks.
See how this workshop works Behind the scenes shows how it is built, what is inside your repo, and how to build a workshop of your own.

Still the sample person? Add your content

Your site still shows Ada Example, or it is not live yet? Open your portfolio folder in Antigravity IDE and run the Roles again, each in a fresh chat, starting with Start the Analyst step. The step pages, from Analyst to Ops, work at home as in the room.

Take your site further

Your site is live. Three things make it even better, each in a fresh chat in your portfolio folder.

Design your page with Stitch: a unique design that fits your style. Today your site wears your style's ready-made design. Stitch, Google's free AI design tool, gives it a look that only your site has. Ask the Designer: Write my Stitch prompt. It writes the prompt from your answers, and turns the design you make in Stitch into a new brief; the Developer builds it in the next fresh chat. The steps are on the Designer page: Try it at home.
QA, the check before you publish. QA looks at your site the way visitors do: on a phone, in dark mode, and how fast it loads. It catches what the person who built a page no longer sees, such as text too pale to read, a layout that breaks on a phone, a button you cannot reach with the keyboard, or a page that loads slowly on a train, and it proves each fix with a new screenshot or a number. Type Start the QA step. The QA page walks you through it. Only a few minutes? Look at your site on your phone, switch your computer to dark mode and look again, and run the Check: node tools/check.mjs.
More of your story. Add projects with their GitHub links, the events you spoke at, or anything else your CV does not say: ask the Analyst for it.

The files that steer your agent

Your repo came with a few Markdown files (.md, plain text with headings) that tell the agent what to do. They stay in your repo, so the Roles work at home exactly as in the room. Open them in Antigravity IDE and read them: they are written in plain English.

AGENTS.md, the rules. Antigravity gives this file to the agent in every chat: the five Roles in their order, one Role per chat, read every change back before you accept it, and load nothing from other servers. Add a rule of your own at the end, in one plain sentence, and the agent reads it in every chat.
.agents/skills/, one skill per Role. Each folder has a SKILL.md: a short description at the top, then the Role's steps. The agent reads only the descriptions, and opens the one that matches what you type. That is why Start the Analyst step. starts the Analyst: its description says so. There are more skills than Roles: the help mode (Where am I?), Explain … to me, Write down what we did and why, the legal page, the checkpoints and the Optional modules.
docs/spec.md and design/brief.md, the memory. The Analyst's spec and the Designer's brief carry the work from one Role to the next, so a fresh chat loses nothing. Change them by asking the Role that wrote them.

To continue at home, start a fresh chat and type the Role's prompt, as in the room. To build a skill of your own, copy one folder in .agents/skills/, rename it, and rewrite its description and steps for your task. What each file in your repo does explains every file, and Build your own AI system shows how these skills were written and tested.

Add an Optional module

An Optional module is one more section for your site: YouTube videos, podcasts, a blog, resources you recommend, or project ideas. Each entry is a link, shown as a card below your CV.

Start a fresh chat and check the model, as in every Role.
Ask for the section you want, for example:

Agent chat

Add a YouTube section to my portfolio.

The agent asks you for each entry: a title, a link and, if you like, a sentence about it. It writes them into your content file and shows you the new section in the preview.

The same kind of chat adds a widget: your events and talks, certifications, a dated "Now" list, a few numbers, or a project told as a case study. For example: "Add my certifications to my portfolio."

Publish it: start a fresh chat and type:

Agent chat

Start the Ops step.

Keep editing

To change your content, edit site/content.json in Antigravity IDE, or ask the agent in a fresh chat, for example:

Agent chat

Change my headline in site/content.json to "Frontend developer who builds fast, accessible sites". Then run node tools/check-content.mjs.

Then publish with Ops, as above. Leave the Analyst out of small changes: it rewrites the whole content file, so the Optional modules you added would be gone.

Your legal page has a helper of its own. Ask in a fresh chat, for example "Add my postal address to my legal page." or "Translate my legal page into Italian." It writes the page again with node tools/legal.mjs and reads it back.

To see your changes before you publish, start the preview in the terminal of Antigravity IDE (menu Terminal → New Terminal):

Terminal · same on Mac, Windows and Linux

node tools/preview.mjs

It prints an address such as http://localhost:8000. Open it in Chrome. The preview keeps that terminal busy until you stop it with Ctrl+C, also on a Mac.

Publish without the agent

Open a second terminal with Terminal → New Terminal, or stop the preview with Ctrl+C first. Then paste these commands one at a time (Cmd+V on a Mac, Ctrl+V on Windows, Ctrl+Shift+V on Linux), press Enter after each, and read what it prints before the next.

First, see what would be published. Read the list as Ops did: only files in site/, and maybe design/brief.md or docs/spec.md. Move anything else, such as a CV, out of the folder first.

Terminal · same on Mac, Windows and Linux

git status

Add the changes:

git add -A

Save them in a commit:

git commit -m "Update my portfolio"

Send them to GitHub:

git push

A Mac remembers the token from the workshop. Linux asks for one at every push: make a new one the same way, as in Sign in if GitHub asks.

Wait until the new version is online:

node tools/live.mjs

Done when it prints Your site is live.

Add a font that is not in your repo

Your site loads no font from another server: that would send every visitor's IP address (the number that identifies their internet connection) to that server. So the font files go into your repo.

Open fonts.google.com, search for the font, click Get font, then Download all.
Unzip the download:

Double-click the downloaded file in your Downloads folder.

In your portfolio folder, open site, then assets. No folder called fonts there yet? Create it: in Finder with File → New Folder, in File Explorer with New → Folder, in Files with a right-click and New Folder.
Copy all the files from the unzipped folder into fonts, the licence file too.
Start a fresh chat and ask the Developer to use it, for example "Use the font Lora from site/assets/fonts/ for the headings."

A shorter address

Want an address without /portfolio/ at the end, such as https://YOUR-USERNAME.github.io/? Rename your repo:

In your repo on GitHub, open Settings. Under Repository name, rename portfolio to YOUR-USERNAME.github.io, with your own username, and click Rename.
In Antigravity IDE, start a fresh chat and tell the agent:

Agent chat

I renamed my repo on GitHub to YOUR-USERNAME.github.io. Update the remote of my local repo to the new address.

Publish once with Ops. Your site then lives at the shorter address.

Learn with your agent

Your agent is also a teacher. Ask it about anything it built, in a fresh chat:

Agent chat

Explain site/index.html to me.

It explains the file in plain words, points to the lines, and asks you one question to check you got it. It changes nothing. Ideas work too: Explain dark mode to me.

Let it also write down what you did and why. It saves the story of your site, Role by Role, in docs/recap.md in your repo:

Agent chat

Write down what we did and why.

Then go further: Do it professionally shows what changes on a real project, three deep dives explain web development, AI and the building blocks, and Agentic frameworks gives you three flows to try.