Website design and development

A site is a channel with numbers on it

A corporate site is judged on two things: whether someone who has never heard of you understands what you do in the first ten seconds, and whether the people looking for what you sell can find the page at all. Animation, photography and clever layout only start to matter once those two hold.

So we start from the pages rather than the homepage. What does a buyer need to read before they get in touch? Which questions do they ask on the phone that the site should already have answered? The homepage is assembled last, out of what the other pages proved was worth saying.

Static by default, dynamic where it pays for itself

This site is built with Next.js and generated statically: every page exists as HTML before anyone requests it, so there is no rendering work at request time and nothing to fall over under load. For a corporate site, a product page or a landing page that is the right default, and it is cheap to host.

We move to a dynamic setup when there is a real reason: a catalogue that changes daily, a customer login, a form that writes to a database, a listing with filters. That decision is made once, explicitly, at the scope stage, because retrofitting it later is the expensive version.

How a site gets built

Content and structure first. We agree the page list, the URL structure and roughly what each page has to say. A site whose navigation is designed after the pages are built always reads like it.

Design on the pages that matter. Layouts are produced for the home page, a service or product page and contact, then reviewed in the browser at phone width rather than only as a flat image.

Build and content load. Pages are implemented, the real text and images go in, and the site goes onto a preview URL your team can open and comment on.

Pre-launch checks. Speed on a mid-range phone, heading structure and alt text, metadata and social previews, forms tested end to end, and redirects mapped from the old URLs so existing search results do not break.

Launch and the week after. DNS, certificates, analytics and Search Console. We watch the crawl and the error reports for the first days, because that is when an overlooked redirect shows itself.

Two languages, one site

This site runs in Turkish and English from one content file per language, with hreflang tags so search engines read the pages as translations of each other rather than duplicates. Each language gets its own URL and its own metadata.

The part people underestimate is that a second language doubles the editorial work, not the build work. We set the structure up so a page cannot ship in one language and quietly stay missing in the other.

Content you can change without calling us

Where content changes often, we connect an editor so your team can publish without a deployment. Where it barely changes, a content file the developer edits is simpler and faster than a system nobody logs into. We recommend based on how often you actually publish, not on which option sounds more capable.

Speed is a budget you spend, not a feature you add

Every font, tracking script and hero video comes out of the same budget: how long a visitor waits on a mid-range phone over mobile data. We keep that budget visible during design instead of discovering at the end that the page weighs more than optimisation can fix.

Images are sized and served in modern formats, fonts load so text is readable immediately, and every third-party script is a decision someone made rather than a default that crept in.

What handover includes

The repository, the hosting setup, the domain and DNS records under your own accounts, and analytics and Search Console connected to your addresses. If you later move the site elsewhere, nothing is held hostage inside an agency account.