Portfolio sites get delayed more than almost any other kind of website, and it's rarely because the work isn't ready. It's template paralysis: scrolling through options, second-guessing layouts, and never actually publishing anything.
Strip away the indecision and most portfolios need the same handful of things: a short introduction that says who you are and what you do, a selection of your best work, a way to contact you, and, depending on your field, a resume or case-study link. That's the whole job. Custom animations, elaborate page transitions, and a dozen navigation options aren't requirements; they're what causes the delay in the first place.
A useful prompt covers four things: your field or role, roughly how many projects or samples you want to show, the tone you're going for (minimal, bold, colorful, text-focused), and any must-have sections (About, Selected Work, Contact, Resume). One of the example prompts on Nova's own homepage is simply "Portfolio site." But the more specific your version is, the closer the first draft lands to something usable.
Example: "Portfolio site for a freelance graphic designer. Six projects, image-focused, minimal black-and-white style, with an About section and a contact form."
The more your prompt sounds like a description you'd give a person, the better: mention the industry norms you already know about (a photographer's site should be almost entirely images; a copywriter's should be almost entirely text) so the draft starts closer to right.
The generated draft is a starting point, not a finished product. Expect to swap in your actual project images and descriptions; add real contact information and social or portfolio links (Behance, GitHub, LinkedIn, whatever's relevant to your field); reorder projects so your strongest work leads, since visitors rarely scroll through everything and the first one or two projects carry the most weight; and trim or rewrite any generic-sounding placeholder copy so it sounds like you.
A photographer or designer's portfolio should be image-heavy with minimal text getting in the way. Let the work speak. A writer's portfolio works better as text samples and links to published pieces, with just enough framing to give context. A developer's portfolio benefits from project descriptions paired with links to live demos or repositories, since people evaluating developers usually want to click through and see something working. A freelancer or consultant's portfolio usually needs a services list and, if you have them, a couple of client testimonials. Those do more convincing than any amount of design polish. Musicians and performers tend to need embedded audio or video near the top, above everything else, since that's what people actually came to check. Architects and other visually technical fields often need larger project pages with multiple images per project rather than a single grid. Worth specifying that in your prompt if it applies to you.
Keep project descriptions short: a sentence or two on what the project was and your role is usually enough; a wall of text under every thumbnail discourages people from looking at more than one. Make sure image file names and alt text describe what's actually in them rather than being left generic, since that helps both accessibility and how search engines understand your page. And don't bury your contact method. It should be reachable from anywhere on the site, not just a page three clicks deep.
Most portfolios start without a proper shoot, and that's fine: decent, well-lit photos of real work, or of you if the portfolio is service-based, beat empty placeholders every time. If a project only exists as a rough export or a phone photo of a finished piece, use it rather than waiting for better documentation to happen someday; you can always swap in higher-quality images later without touching anything else on the page. A portfolio with three real, slightly imperfect examples beats an empty one waiting for a photographer's schedule to open up.
If you're newer to a field and don't have client work yet, coursework, personal projects, and self-directed pieces are legitimate portfolio content. Frame them as what they are rather than trying to make them look like paid client work they aren't. A short note on what you learned or built independently often reads better to someone hiring or commissioning work than an empty portfolio waiting for "real" experience to accumulate first. Mention this context in your prompt too: "portfolio for a recent design graduate, mostly coursework and personal projects" gets you a draft that frames things appropriately, rather than one that implies a client history you don't have yet.
It's tempting to keep regenerating a portfolio looking for the "perfect" version before publishing anything. Resist that. A live portfolio with real work on it, even in a fairly plain layout, does more for you than a perfect-looking draft sitting unpublished while you keep tweaking it. You can always regenerate sections or adjust the design after it's live; what matters most early on is that there's something real for people to see when they look you up.
Not to start. A blog is worth adding later if you want to demonstrate expertise or improve search visibility over time, but it's not part of the core job a portfolio needs to do on day one.
Enough to demonstrate range without diluting quality. Five to eight strong pieces usually beats fifteen mixed ones. Lead with your best regardless of how many you include.
That depends on your field and how you sell your services. Freelancers and consultants often benefit from at least a starting-price range or a "get a quote" path; creative portfolios where the sale happens through a longer conversation can leave it off entirely.
You don't need six weeks and a mood board. Describe your field, your work, and your tone, generate a draft on Nova, and spend your remaining time on the part that actually matters: making sure your best work is the first thing a visitor sees.