An art exhibition website for one show, from private view to close

Show site or portfolio?

A portfolio is ongoing and organised around the artist: selected work across years, a CV, commissions. An exhibition site is temporary and organised around the show: its title, its idea, the works hung together, the dates. Group shows, degree shows, open studios and pop-up exhibitions all need this kind of site, often with several artists and no single owner. If you're building something permanent for yourself as an artist, start from a portfolio instead and add the show as a page.

The visit block

• Title and artists, as on the poster.
• Dates: the opening, the run and the last day, in that order.
• Opening hours for each day, including late openings and closures.
• Address and access: entrance, step-free route, nearest station, parking.
• Admission: free, ticketed or by appointment.
• Events: artist talks, tours, workshops, the closing party.

The works list

The list of works is the heart of the site and the part people return to. Each work needs an image and the standard tombstone details. In Anticode, keep them in a CMS collection with typed fields, edited in the dashboard, so each work gets its own page at /works/<slug> and a change to a price or a sold dot doesn't mean rebuilding the site.

Photograph works square-on in even light, and add them to the build; describe each in its alt text, which the design gate requires before publishing and which is how visually impaired visitors will meet the work. The alt text guide has examples for artworks.

Statements

One exhibition statement of two or three paragraphs, in plain language, says what the show is about. For group shows, give each artist a short statement and a link to their own site. Avoid gallery jargon; a visitor should be able to read it on the bus and arrive knowing what to look for.

The private-view RSVP

An RSVP gives you numbers for drinks and space and a list of people interested in the work. Use the contact form, which asks for a name, an email and a message (say above it to include the number in their party), or the newsletter form if an email address is all you need. Don't use the booking calendar for this: it allows one booking per time slot, which suits a studio visit by appointment but not a crowd at an opening. Each RSVP is saved in your dashboard and can go to a Google Sheet through a connector.

Selling work

Most galleries handle sales by enquiry, and the contact form does that well: a collector writes about a piece and you reply. For editions or smaller works at fixed prices, a buy button can open a payment link from your provider. There's one payment link per account, so make it a product list at the provider with each work as an option. Mark works as sold promptly by editing the collection entry.

Building it

Describe the show: "a website for 'Edgelands', a group exhibition of six painters at Bankside Studio, 3 to 22 November, with a works list, artist statements, opening hours and a private-view RSVP". Swiss (Inter Tight) and Editorial (Geist) give the work room. After the show closes, replace the visit block with "This exhibition has closed" and keep the works as an archive, or export it as a single HTML file for the artists.

Limits

• No virtual 3D gallery on a design-engine page. An app build can draw an interactive view, but treat it as an extra.
• No checkout or cart. Sales go through enquiries or payment links.
• No visitor accounts or wish lists.
• No ticketing system for timed entry.

Questions people ask

Should I show prices on an exhibition website?

It's increasingly common and saves collectors an awkward email. If some works are priced on request, say so consistently.

Can several artists edit the works list?

Yes, if they're members of a Team workspace with access to the project.

How long should the site stay up?

As long as it's useful. A closed show is still a record of the work, and artists link to it from their CVs.