Ongoing development for a Melbourne tailoring house
Deorum's website was already built and live when this engagement began. The work since has been search infrastructure, enquiry flows, and an automated test suite.
Synetra's role: Ongoing development on an existing website, from 2026. Synetra did not build the original site and has not been its only contributor. Published with the client's permission.
A Toorak tailoring house
Deorum is a private made-to-measure tailoring showroom in Toorak, Melbourne, seen by appointment. The website's job is to communicate a standard and to get the right person to book an appointment.
Nothing is sold online. The conversion event is an enquiry or an appointment request, so the forms have to be reliable, and the pages describing the house and its makers have to be findable.
What the engagement covers
The site is a SvelteKit application, prerendered to static pages. Work arrives as requests from the client and is delivered against the existing codebase.
Technical SEO layer
Per-page metadata, structured data, breadcrumbs and a generated sitemap that picks up new routes automatically.
Enquiry and appointment flows
Form validation, spam guards, in-page confirmation states and automated replies.
Staging environment
A place to review a change before it reaches the live site.
Automated test suite
Browser-level and accessibility checks run against the built site before each deploy.
Additional pages
New pages and sections built against the existing design system as the house has asked for them.
Ongoing changes on request
Content updates and adjustments handled as they come up.
The site organises its makers into several taxonomies, and each addition used to be a manual step that could be forgotten. Generating the sitemap from the routes that exist means a new page is discoverable the moment it ships.
Inheriting a codebase you did not write
The risk in taking over someone else's codebase sits in what you have not read yet. The approach here was to build the safety net before making changes at pace: a staging environment so nothing is tested in production, and an automated test suite so a change in one part of the site cannot break another.
The services page covers how takeover engagements are scoped, including the code audit that comes first.