Send the work as a website.
A prototype opened in a browser, on the device it was drawn for, gets better feedback than the same prototype in a screen share. If your tool exports HTML — and most of them do — that export is already a website looking for an address.
Where designers reach for this
The exported prototype
An HTML export from your design tool, or something a developer coded from your file. Drop the folder in and it has a URL a minute later.
The portfolio
Your own markup, your own type, none of a template marketplace's opinions about how a case study should look. Claim it and the subdomain is yours to pick.
Feedback from a phone
A good share of the notes you get back are about how it feels at 390 pixels wide. A link is the only way anyone finds that out before it's built.
From a folder to a link
- 01
Export or code the thing
Anything that produces a folder with an index.html in it works, and the assets it references come along as long as the paths are relative.
- 02
Drop the folder in your browser
Drag it onto the page. No terminal, nothing to install, and no account needed for the first one.
- 03
Claim it and name it
A free account lets you set the subdomain and redeploy over the same address as the work changes, so the link you sent last week still shows the current version.
Pick how you drive it
All of these publish the same way and produce the same site. The only difference is what you already have open.
- 파일 드롭Drag the folder onto the page. For most design work this is the entire workflow, start to finish.
- AI 빌더Describe a page and get HTML back when you need something standing up before the real design exists.
- 커맨드라인One command, for when a developer has already built the thing and you're the one publishing it.
Put something online and see
The first deploy needs no account: drop a folder in and a live URL comes back, along with a private claim link if you decide to keep the site.
Put a site onlineQuestions from designers
I don't use a terminal. Will anything here require one?
No. Dragging the folder onto the page in your browser is a complete deploy, and everything afterwards — renaming, replacing, deleting — is in the dashboard.
Will my fonts and images come through?
Yes, as long as your HTML references them with relative paths, which is what an export produces. The folder is served exactly as you uploaded it, with the same structure.
Can I put a contact form on my portfolio?
Yes, and without a form service: add harvis-form="contact" to your own form markup and the submissions land in your dashboard, spam-filtered, with a thank-you page you don't have to design.
Do I need an account?
Not for the first deploy. You get a live URL and a private claim link; the claim link attaches the site to a free account when you want to choose its subdomain, redeploy over it, or delete it.
What can harvis not host?
Anything that needs code running on a server: PHP, Node, Python, a database, or a page rendered at request time. harvis serves the static files you upload and collects submissions from forms on them. A JavaScript front end talking to an API hosted elsewhere works normally.
What does it cost?
Publishing is free — 500 files and 50 MB per site, no card, and sites that do not expire. If a month outgrows the free limits the account steps onto the nearest paid step, from $5, and steps back down when usage does. Bandwidth and SSL are never billed.
Is someone else's job closer to yours?
The product underneath is the same — these pages just start from a different problem.