Skip to content

Gallery · reads media

Portfolio

Showcase of work.

Images at full width, arranged to be looked at.

"Role" is the field most portfolios omit and every client asks about.

Café Bellevue fit-out

Café Bellevue

Autumn range identity

Atelier Nord

Maison Lauret rebrand

Maison Lauret

Rue Oberkampf shopfront

Self-initiated

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Every field is one a prospective client asks about: who it was for, when, and what you actually did.

Role is the field most portfolios omit and every client asks, usually in the first call.

Public by default, because the point is to win the next job rather than to archive the last one.

How it works

  1. 1

    Finished work is added with its client, year and role.

  2. 2

    The role is required, because it is the first question in every enquiry call.

  3. 3

    The agent answers have you done anything like this from these rows.

  4. 4

    Public by default — the point is to win the next job, not to archive the last one.

Best for

Photos, generated packs, anything where the picture is the content.

Not the right choice for

Records that happen to have a thumbnail — that is Cards.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

FieldTypeFilled from
ProjectrequiredtextWhat it was, named as a client would refer to it.
ClientrequiredtextWho it was for, or Self-initiated. Both are credible.
YearrequiredtextWhen. Recent work reads differently from old work and hiding the date fools nobody.
RolerequiredtextWhat you actually did. The field most portfolios omit and every client asks about.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

  • No case study depth here; a project needing a narrative wants its own page.
  • Client names are public, which needs permission you may not have.
  • No filtering by industry or budget unless you put it in the project name.
  • Nothing measures whether a portfolio piece actually generates enquiries.

Before it works

What you have to provide, if anything.

  • Get permission before naming a client. It is the one field with legal weight.
  • Pair with Image collection when a project deserves a sequence rather than one photograph.

In practice

A studio whose portfolio showed work without saying what they had done on it.

The Bellevue fit-out was design and build, 2026.
What was said to the agent

What the agent built

A portfolio entry with client, year and role.

What changed

The what-did-you-actually-do question disappeared from first calls. Two enquiries specifically referenced the design-and-build role.

Questions

What data does the Portfolio page use?

It reads media records the agent has collected. Showcase of work. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a gallery the wrong choice?

Records that happen to have a thumbnail — that is Cards. It is best for: photos, generated packs, anything where the picture is the content.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.

Ask for it in a sentence

You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.

Build your agent free

Agents

More

👤
Profile
FAQ