Assess
Is this right for you?
Open Portfolio is version 0.5.0 and it is alpha. Rather than define that word, here is precisely what it means for you, and three groups of people who should do three different things.
Use it
Use it today if
- You are a student or early in your careerA portfolio you own, for the price of a domain, that will not be held hostage when money is tight. The risk of an alpha is lowest exactly here.
- You are already comfortable with GitHubThen the deploy is five minutes and rolling back a bad update is one click. Nothing about the rest of it needs code.
- Your site is words, pictures and a contact formThat is what this does well. Twenty-seven blocks, six themes, real search metadata, an inbox that works.
- You have been burned by a subscriptionContent in your own database, an export button, an MIT licence. The whole design answers this specific grievance.
- You self-host things alreadyOne Docker command, Postgres, no account anywhere, nothing that phones home.
Wait
Wait a version or two if
- You need to edit from a phone regularlyThe admin installs to a home screen and works, but the screens were drawn for a desktop. It is the next substantial piece of work.Not built
- You want a specific visual designSix themes change colour, type, spacing and radius. None of them rearranges a page — arrangement comes from which blocks you place.Bounded by design
- Your work is hundreds of piecesThe whole site is saved as one document on every change. Fine for a portfolio; not the shape for a four-hundred-post archive.Known limit
Don't
Use something else if
- You need to sell anythingNo shop, no bookings, no memberships, no paid content — and none of it is planned. Squarespace and Wix both do this today.
- The visual design is the workIf you are a designer being hired for visual range, Framer, Cargo and Semplice are all better answers to that problem than this is.
- You want somebody to phoneThere is no support desk, no status page and nobody on call. Questions go to one person on GitHub, answered in their own time.
- You will not manage a hostSomebody has to press deploy and own a domain. Wix will publish a site today with an advertising banner on it, and Behance and Contra will give you a profile with no setup at all.
Risk
What “alpha” actually risks
Separating the part that would hurt from the part that annoys.
Your content is the safe part
It is in your database. You can export all of it at any moment as one JSON file. An older build quarantines content it does not recognise rather than dropping it, so a rollback cannot destroy what a newer version wrote. Concurrent edits are detected rather than silently overwriting each other, and the last twenty published snapshots can each be restored.
The admin is the unsettled part
Screens move, get renamed and get rebuilt between versions. If you learn where something is, it may be somewhere else in three months. That is the actual cost of using this now, and it is an irritation rather than a loss.
One maintainer is the real risk
Not that the code is bad — that a project with one person behind it can simply stop. What makes that survivable is the same thing that makes the rest of it work: your site keeps running, your content is exportable, and the licence on what has already been released cannot be withdrawn.
CTA
Twenty minutes will tell you more than this page
The demo gives you a full editor with nothing to sign up for. It forgets you after an hour.