Portfolios
The work,one project to a page.
A portfolio is never finished. A project lands, the pictures arrive a week later, the client asks for the case study to stay off the public site until their launch — and the site that was rebuilt for the last redesign is the reason none of it happens. Built here, a new project is a record, not a rebuild.
One layout,
filled in again and again.
Design the project page once as a component: the cover, the client, the year, the discipline, the gallery, the quote, the result. Its data structure decides what a project consists of, so the next one is a form to fill in rather than a page to build. Change the component later and every project page changes with it.
Keep the projects themselves as a dataset — one record each, with the fields your work actually has — and generate a page per record. The index is a view of the same dataset, so a project cannot appear on the list and be missing from the site, or the other way round.
Drafts,
and the client who is not public yet.
Every page arrives as a draft. A case study can sit in the project finished for a month while the client's own launch date comes round, shared on a hidden preview with a preview code so they can approve the words without it being on the internet, then published on the morning it is allowed.
The pictures are the portfolio, so they live in the media library with their ALT text, tags and licence beside them — and the duplicate check means the same cover is not uploaded four times under four names.
Studios that work in more than one market clone and translate the project pages, and the fields marked translatable carry the descriptions across with them.
- 1Title"Harbour Hotel — rebrand".
- 2Client, yearShown on the card and the page.
- 3DisciplineFilters the index without a second list.
- 4Cover, galleryFrom the library, ALT already written.
- ·DraftFinished in March, public in May.
- 5ResultThe paragraph that wins the next one.
One recordOne page
Adding the project you just finished should take the afternoon it deserves,
not a redesign.
Worth knowing
What carries the weight here.
Projects as records
Typed fields, views and relations, and a page generated for each one. See datasets and content.
Pictures with their paperwork
Uploads, AI images and five royalty-free libraries, with ALT, TITLE, tags and the licence recorded. See the media library.
Seen before it is public
Drafts, a hidden preview with a code, and roles for the people reviewing. See collaboration.
Which plan
A portfolio whose projects are ordinary pages fits Regular at €100 a month. The moment the projects become a dataset with pages generated from records — which is the point of doing it this way — it is PRO at €300. A studio where more than one person writes case studies is what Team, at €500 a seat, is for. Compare plans.
Questions
Can a case study stay private until the client launches?
Yes. Keep the page a draft and share it on a hidden preview with a preview code. Nothing is public until you publish it.
Do I have to use a dataset?
No. Twelve projects as twelve pages is a perfectly good portfolio. The dataset earns its place when the list grows, when the same project has to appear in several places, or when you want the index filtered without maintaining a second list by hand.
Can I bring across the portfolio I already have?
The crawler reads an existing site and prepares its pages — see rebuilding a website. What it cannot do is invent the structure your projects should have had; that part is worth an hour of your own.
Field note: the portfolio that stops being updated is almost never the one that was hard to design. It is the one where adding a project meant opening the code.
Your website next.
Start it today.
Open the editor, describe the website, and publish the first version to a cstmui.com address.
Open castomUI See pricing