How many projects can the site hold?

There is no fixed limit. We have designed content structures that carry a large archive with filters by discipline, year, or client, and the pages stay fast because nothing is queried when a visitor arrives. Past a few hundred entries we group the index into categories and paginate instead of showing everything in one grid.

Can I add new projects myself after launch?

Yes, that is why the content model exists. You either edit Markdown files through a Git-based interface or fill in fields in a headless CMS, upload the image set, and the site rebuilds on publish. We record a short walkthrough for your team and hand over the repository either way.

Will a page full of large images still load quickly?

It will if the images are prepared properly, which is most of the engineering work on this kind of site. We generate AVIF and WebP versions at several widths, set fixed aspect ratios so the layout does not shift, and lazy load everything below the first screen. Gallery pages get tested on a throttled mobile connection before launch.

Do you prepare the image files as well?

You upload the originals and the build generates every size the site needs, so nobody resizes files by hand before publishing. If you want us to prepare the first batch of project images, we do that during the build and document the crops so future uploads match.

What if I need a shop or client login later?

Both are possible as a separate phase rather than a redesign. A store adds product pages, payments, and stock handling, and a client area needs accounts plus a backend. We plan the front end so neither change means throwing away the site.

Portfolio Website Development

Portfolio website development for studios, agencies, and photographers: image-heavy project pages that stay fast, capture enquiries, and update easily.

See our work:

Morrow Hill→OKOK→Vikentilia→

Your best work is already on the site and few visitors reach it. The home page opens with a full-width photograph that takes five seconds to appear on a phone, and the grid underneath was assembled in a page builder, so every new project means dragging image blocks around until the layout stops breaking. Someone who does want to hire you fills in a contact form that asks for a name and a message, then waits.

Portfolio sites fail on the two things the format depends on most: images that load and projects that are cheap to publish. We build sites where both are handled by the build rather than by whoever is editing at eleven at night.

What a portfolio build includes

A portfolio is a small content system with a very visual front end. The pieces are an index of projects with filtering or a defined sequence, a page for each project with its image set and credits, an about page for the studio or the person, a contact route that collects a usable brief, and a way for you to add work without calling a developer.

A standard engagement hands over a project index with filtering, a project template with credits and next/previous navigation, an about page, a contact form with file upload, a content model you can publish into, and the repository in your name with a recorded walkthrough.

We keep these sites static wherever it suits you. Pages are generated ahead of time and images are pre-sized, so a gallery opens quickly on a phone in a client meeting. If you would rather edit in a browser than in text files, we connect a headless CMS and rebuild the site when you publish. Where a site does need a logged-in area or a shop, that becomes a second phase with a backend rather than a patch on the front end.

Who this is for

Design and branding studios working from an archive of past projects, where the index matters as much as the individual pages.

Photographers and filmmakers who publish sets or series and need the images to arrive at a sensible size instead of at full camera resolution.

Architects and interior designers presenting a mix of photography, plans, and drawn elevations on the same page without the layout collapsing.

Agencies in production, casting, or marketing, presenting people, campaigns, or a client roster they keep adding to.

Freelance designers, illustrators, and developers who need one credible page, a work index, and a clear way to be contacted.

Images and load speed

Project imagery is the usual failure point, so the pipeline is decided before design starts. We agree on a small set of crops for every project, a wide hero, a portrait tile for the grid, and a square thumbnail for lists, and we fix those aspect ratios in CSS so the grid does not jump around while images arrive.

Uploads accept the original file straight from a camera export or a designer's folder. The build generates AVIF and WebP versions at three widths and serves them through srcset, so a phone downloads the small file while a retina laptop gets the large one. The first gallery row loads immediately because it carries the page, and everything below the fold lazy loads. Self-hosted autoplay video stays off the home page; we use a poster frame with an explicit play action, or a hosted player that loads when clicked.

Each gallery page gets a weight budget, normally under about one megabyte of image data for the first view on a phone, and we check it on a throttled connection before launch. The same work that keeps the site fast also keeps hosting simple, since pre-sized static pages are cheap to serve from a CDN.

Enquiry capture that produces a usable brief

A portfolio contact form should ask the same few questions you would ask on a first call: what the project is, roughly when it starts, the budget range, and who the decision maker is. We add file upload so a brief or reference images arrive with the message, spam protection so the inbox stays readable, and delivery to your email or your CRM. Every project page carries an enquiry link that names the project, so you know which piece of work brought the enquiry in.

How the engagement runs

The first phase is structure and design, usually one to two weeks on a studio site. We map the project archive into categories, agree on the templates (index, project page, about, contact), and design against real content from your archive rather than placeholder text.

The second phase is the build: templates, the image pipeline, filtering, and the content model. The third is migration, where we move the projects you already have, and it is usually the longest stretch of your own time. The fourth is launch and handover, with a recorded walkthrough of the publishing flow.

A one-person portfolio with ten to fifteen projects normally runs two to four weeks. A studio or agency site with filters, case study pages, and a team section runs four to eight weeks. Adding a shop or a client area is a separate phase, planned after the main site is live.

What it costs

Work is quoted at our flat rate of $39 per hour, or as a fixed scope once we have seen the archive and the template list. The scope drivers are the number of templates, whether you want Markdown files or a browser-based CMS, how much filtering the index needs, and how much of the existing content we migrate for you. For studios with a steady publishing rhythm, monthly capacity plans from $2,699 are an option. The pricing page explains the hourly rate, the monthly model, and typical order budgets.

Proof

OKOK Agency is a platform we built for the casting industry, where actors and agencies each get a tailored profile and a direct route to contact each other. It proves the profile-and-index pattern that portfolio work depends on, running as a live product at okokagency.eu.

Vikentilia is a Cyprus real estate platform on WordPress, built around dynamic property search and listing management for the businesses publishing inventory. It shows the owner-side workflow this service needs: many image-led entries, structured fields, and updates made by staff without a developer involved.

Morrow Hill VisionWorks pairs a Vue.js front end with WordPress as the content system, so interactive search stays interactive while the content stays editable. It is the same split we use on studio sites, where the visitor gets a fast interface and the owner keeps control of the content.

Related services

Web development covers the wider front-end and back-end work, including the backend pieces a portfolio sometimes grows into
Design for brand, layout, and typography work when the visual direction is not settled yet
Zero-maintenance static website when the priority is a site with no database and no plugin update cycle
Website redesign and UI refresh if you already have a portfolio that looks dated or performs badly
Figma to HTML development when a designer has produced the layouts and needs them built accurately

Next step

Send a link to your current site, or to the work you want on the new one, and we will say how many templates it needs and how long it takes.

Contact us with the project list, or run your requirements through the Vasilkoff.info estimator to get a first scope and cost range before you talk to anyone.