Explicit widths, not "mobile-friendly"
Layouts and interactions checked against stated viewport widths, including 320 and 375 pixels, with space between content and screen edges, comfortable touch targets and no horizontal overflow.
Dizzyology · Mount Waverley, Melbourne
Building a specialist site without rewriting the specialist.
Approved designs, supplied clinical copy and an explicit instruction not to change either. Wicked built the website so both survived the move to the web intact. Live on www.dizzyology.com.au since 1 September 2026.
The brief
Start with what is already decided.
Dizzyology is a specialist vestibular audiology clinic. The project arrived with approved visual designs by Designable Studio and a supplied copy deck. The instructions were unusually clear: keep the copy verbatim, follow the approved design PDFs, use the established brand colours and typography, and flag missing material rather than invent filler.
Constraints like that are valuable on a specialist project. A sentence that looks long to a developer may carry a distinction the clinic needs. A layout that seems easy to simplify may already have been agreed with the designer. The build's job was to make those decisions usable at every screen size, not to reopen them.
ClientDizzyology
Visual designDesignable Studio
ScopeWebsite build, content manager, handover
Live since1 Sep 2026
What was checked
A desktop design is the beginning of the responsive work.
One fix, all layouts
A global CSS fix once caused a wider mobile regression on this build. Shared styling changes were re-checked across page types, not just the homepage.
Useful before the script runs
Astro generates the public site as static HTML. Content is rendered in the page, with JavaScript enhancing interactions rather than being the only way to reach the information.
Problems flagged, not hidden
A contrast conflict in the approved design was flagged rather than silently changed. Respecting the design and identifying a problem in it are both part of the job.
The handover is another interface
The build includes a Git-backed content manager, separate from the public site. The handover on 7 September 2026 included a manual for editing, reviewing and publishing.
A build record, not a result
This page reports that the site launched and the handover was completed. Increased bookings or improved patient understanding were not measured and are not claimed.
Before a specialist build
Three questions that make the work easier to define.
Who owns the design and the wording, and what may the builder change?
Which page types and screen sizes will be shown during review?
How will the owner edit, review and publish content after handover?
Have an approved design that needs a careful build?
Tell us what is ready and what still needs solving.
Start your project brief