Public sites
Brand and service websites
Lean, polished sites for people who need to be understood quickly and contacted easily.
Websites and platforms that are built to be used.
Practical websites for people, projects, events and small businesses that need to look sharp, explain the offer and make the next step easy.
A good site should look sharp, explain itself quickly and make the next step obvious.
A useful website starts with a strong first impression, clear routes through the work, and enough structure to grow without becoming messy.
Website work can be simple and polished, or more operational when a project needs content updates, event flows, forms, media handling or product-style thinking.
The sweet spot is a useful, manageable build: enough structure to work properly, without turning a small project into a huge platform it does not need.
Types of web build.
The site offer can flex from lightweight public pages to more involved platforms with content and workflow needs.
Discuss a site
Platforms
Event and project systems
Structured pages, submission flows, media areas and admin-friendly content for projects that have moving parts.
Refreshes
Sharper existing sites
Copy, layout, photography and user journeys tightened so the site feels more professional and easier to use.
Platform work
Maui Waui Festival platform
A festival platform built around real operational needs: public information, artist and trader flows, data handling, media, messaging and reliable infrastructure. It is the sort of project where design, product thinking and practical engineering all have to meet.
Clear sites, practical systems and honest boundaries.
The first conversation is about what the website needs to do, how much should be built now, and what can sensibly wait until there is more evidence behind it.
Works well for
- Portfolio, service and project websites that need stronger design and clearer wording.
- Small business sites where contact, trust and local reputation matter.
- Event or community sites with practical pages, updates, forms or media needs.
- Existing websites that need tightening rather than starting again from scratch.
Needs a different route
- Large ecommerce stores with complex stock, fulfilment and payment operations.
- Enterprise systems that need a full software team, support desk and long-term maintenance contract.
- Projects where the brief is already fixed and just needs anonymous production work.
- Anything better handled by a trusted specialist, where Dibs can help point you in the right direction.
What a web project can include.
This can be kept lightweight, or built out properly when the project needs a more complete digital base.
Direction and content shape
What the site needs to say, who it is for, and which pages deserve space.
Design and build
Responsive pages, strong visual hierarchy, sensible navigation and practical content blocks.
Review and refine
Wording, images and structure are tightened before the site is put in front of the wider world.
Before building, get the basics straight.
A site gets easier to design when the offer, audience, content and next step are clear enough to make decisions from.
Offer
What should people understand first?
The homepage needs to make the offer obvious quickly, without forcing visitors to decode it.
Audience
Who needs to trust it?
A workshop visitor, local customer, trader, event organiser or client may all need different proof.
Content
What exists already?
Images, old pages, logos, copy, screenshots, event info and rough notes can all be shaped into a better structure.
Action
What should happen next?
Contact, booking, enquiry, download, reading more or simply understanding the project should be designed deliberately.