AI Portfolio Website Builder: From Prompt to Live Domain

An AI portfolio website builder works like this: you describe the sections you need in plain text — a hero with your name and specialty, a work gallery, an about block, contacts, and an inquiry form — and Zugo generates the finished page in about a minute and verifies it in a sandbox as it opens. Then you refine it by chat, publish in one click to your-project.zugo.run, and connect a custom domain on Pro. No code involved.

Below: exactly what to put in the prompt for the gallery and the inquiry form, a copy-paste prompt template, a table of emphasis points for four portfolio types, and an honest look at the cases where this approach won't work.

What should you write in the prompt for a portfolio site?

The quality of the first build largely comes down to the prompt. A portfolio has five working sections, and it pays to list them explicitly rather than hope the builder guesses — you'll have almost nothing left to fix afterward.

• Hero. Name, specialty, a one-line offer, and a "View work" button. This is the screen where visitors decide whether to keep reading or close the tab.
• Work gallery. A grid of projects with a preview, title, and your role. Naming a number matters here: "6–9 cards" produces a predictable grid, "show my work" produces a lottery.
• About. A photo, three or four sentences about your experience, and a list of skills or tools. This is also the place to mention who you've worked with.
• Contacts. Email, links to social profiles or industry platforms.
• Inquiry form. Name, email, message — wired to send you an email so no lead gets lost.

Here's a prompt you can copy and fill in with your own details:

Build a one-page portfolio site for a [profession], name [name].
Sections in this order:
1. Hero: name, specialty, one-line offer, "View work" button.
2. Gallery: grid of 6–9 projects, each with a preview, title, role, and link.
3. About: photo placeholder, 3–4 sentences of experience, list of skills/tools.
4. Contacts: email, LinkedIn, social links.
5. Inquiry form: name, email, message — sent to my inbox.
Tone: [restrained/bold], dark theme, clean typography.

If you'd rather not start from a blank page, Zugo ships 25 templates across five categories: pick the one closest to a portfolio and rewrite it in your own words. The result is more predictable than a fully freeform prompt. The general mechanics are covered in the guide on making a website with AI; here we're narrowing down to portfolios specifically.

Which details matter for your type of portfolio?

A designer's, photographer's, developer's, and copywriter's portfolios are four different sites, even though the sections are the same. The difference is what goes up front and how the gallery is tuned. Here's what to emphasize in the prompt for each case.

The logic is simple: visual professions push the gallery forward with bigger images; text and technical professions lead with specifics and links to results. Drop the relevant line from the right column straight into the prompt from the previous section, and the first build will land much closer to what you need.

How do you build and publish it, step by step?

The process is the same for every portfolio type.

1. Describe the portfolio in text, or start from a template. No card required: free starter credits cover the first build and publish. Open Zugo, paste your prompt.
2. Wait for the build to verify. While the agent works, you watch a live process log with a timer — you can see which file is being created right now. A typical portfolio page assembles in about a minute; a multi-page build takes a few minutes. The "verified" status means the site went through the sandbox and actually loaded and rendered in the preview — not just "code was generated."
3. Refine by chat. The first version is a draft. "Make the gallery previews larger," "move the inquiry form above the contacts," "rewrite the headline as a question." Every edit goes through the same build-and-verify cycle, so you never see a broken state. To avoid repeating style notes in every message, save a workspace skill — "dark background, no stock photos, formal tone" — and the agent keeps it in mind on its own.
4. Publish in one click. One button, and the site gets a your-project.zugo.run address you can send to a client or post on socials right away.

What do you need for a custom domain, working inquiries, and analytics?

The zugo.run subdomain is fine for showing your portfolio around and collecting first responses. For a professional site you'll want three more things, and all of them connect without code.

A custom domain. Available on Pro at $25/month. Pro includes 200 credits — roughly 16 full platforms or 33 quick builds and edits — plus custom domains. Teams and agencies have Business at $99. The breakdown is on the pricing page.

An inquiry form that actually delivers. As long as the form merely "exists on the page," inquiries go nowhere. The Resend connector makes it email you on every submission. For a portfolio this is the critical block — it's the whole reason the site exists.

Analytics. The Google Analytics connector shows how many people opened the portfolio, where they came from, and whether they reach the form. Without numbers, you can't tell if the page is working or sitting there dead.

And there's an exit from lock-in: the code isn't trapped inside the builder. GitHub export creates a real repository with a standard scaffold (src/, package.json, vite.config), and the Vercel connector deploys the site to your own account. If the portfolio grows into a full studio site, a developer gets a normal project, not a black box.

Where can you see examples first?

Before writing your own prompt, it's worth opening the showcase gallery: it holds published user projects, including one-pagers and landing pages structurally close to a portfolio. Pick one that matches your taste, see how the sections are arranged, and describe your own version in text. The same mechanics let Zugo build not just sites but mini-apps and 2D games — if you ever want to add something interactive to your portfolio, see the guide on building an app with AI.

When won't this approach work?

Honest boundaries, because portfolios differ.

Pixel-perfect reproduction of a mockup. If you have an approved Figma design and you check spacing down to the pixel, hand-coding it is faster than chasing an exact match through chat edits. The builder will get close and keep it clean, but "exactly like the mockup" is not what it's built for.

A gallery of hundreds of heavy photos. A photographer with a multi-gigabyte archive needs dedicated media hosting or a CDN for images. Zugo will build the site frame itself, but uploading hundreds of full-resolution originals into it is a bad idea — ask for links to external storage plus lazy loading instead.

Everything in between is workable: build the portfolio in an evening, put it on your own domain, wire up the form and analytics, and if the project outgrows the page, take the code via GitHub and continue with a developer.

Frequently asked questions

Is it free?

Starter credits come without a card — enough to build and publish your first portfolio on a zugo.run address. A custom domain, the Resend connector for inquiries, and a bigger limit come with Pro at $25/month.

Will inquiries arrive in my inbox?

Yes, if you connect the Resend connector to the form. Without it the form renders, but the emails go nowhere. It's the first thing to set up after publishing.

Can I take the code and move it to my own hosting?

Yes. GitHub export hands you a regular repository (src/, package.json, vite.config) that opens in any editor and deploys anywhere — including your own Vercel account via the connector.

Can I build more than a one-pager — a multi-page site?

Yes. That's what Plan mode is for: the builder first shows the page structure, you approve it, then the build proceeds by plan with checkpoints. It's a convenient way to add separate case-study pages or a blog to your portfolio.