Web Design + Development.
PROCESS
-
Discovery + scope
Goals, content and technical ground are set; scope is fixed in writing.
-
Art direction
Concept, type and motion language; no production without approval.
-
Build
Static HTML + GSAP, native browser scrolling; performance budgets applied from the start.
-
Measure + handover
Accessibility and speed audit; documented, maintainable delivery.
WHAT’S INCLUDED
- Editorial design + type system
- Multilingual architecture (TR · EN · DE)
- Motion choreography — reduced-motion included
- Accessibility: AA baseline
- Performance: built to LCP < 0.8s
MEASURED DIAGRAMS
Largest Contentful Paint — three live projects
Layout shift — three measured values
JavaScript weight — weighed on every build
SCOPE
Corporate web design: who it is for
Corporate web design here does not mean “large company”; it means a site that speaks several languages, is touched by several teams and has to live for years. At that scale what decides is not the visual but the contract: design tokens, schema at template level, and audits that run before release. This site itself was built under that contract.
Premium and custom web design — why no template
Custom web design is chosen because it is measurable, not because it is expensive. A ready template is fast on day one and heavy in month three: unused scripts, components that cannot move, accessibility that breaks. Premium web design is not an adjective in this repository but a budget line — the JS budget and critical CSS are written first and defended by a guard.
Custom website development: multilingual architecture
On a three-language site the cost accumulates in architecture, not translation: URL structure, x-default, the language switcher and schema translations. That is exactly why custom website development is chosen — these layers cannot be added later, they are built on day one. The example is live on this site: three languages, a reciprocal hreflang cluster, one generator.
For manufacturers and exporters
Sites that carry a product catalogue, certificates and a quote flow have rules of their own: product information on the page rather than in a PDF, every market in its own language, a sale that starts with a request for quotation. The details are on the B2B websites page.
Speed as a separate engagement
Every new site ships with a performance budget. If you already have a site that is slow, speed can be a job of its own: we trace why pages are slow for real visitors and fix it at the source — Core Web Vitals optimization.
LOCATION: ISTANBUL
Istanbul, TR — remote by default; on site when it matters.
FREQUENTLY ASKED QUESTIONS
-
How is web design pricing determined?
Price is set by scope in a written quote; no package list is published. Three variables carry the cost: how many templates, how many languages, how many third-party systems. The same content in one language and in three is two different projects — language count grows the architecture more than the translation.
-
Why is custom web design more expensive than a theme?
Higher build cost, lower cost of ownership. A ready theme is fast on day one and heavy in month three: unused scripts, components that cannot move, accessibility that breaks on update. In a custom build the budget is written first and defended by a guard.
-
Is multilingual setup included?
Yes, multilingual architecture is part of the build: a separate URL tree per language, reciprocal hreflang, x-default and a language switcher. Translation itself is a separate item — you supply the text, or translator coordination is added to scope.
-
Can my current site be made faster without a rebuild?
Usually yes. The audit first says what is possible on your existing stack; image formats, critical CSS, script budget and cache headers rarely need a rewrite. If the gain is not worth it, we say so with numbers.
-
What accessibility level is applied?
WCAG 2.2 AA is the baseline and is not priced as an extra: AA contrast, visible keyboard focus, ≥ 24 px touch targets, and a full alternative flow for reduced motion. The audit is done state by state, not by an automated tool alone.
-
What is the site built with?
Static HTML, vanilla JavaScript and GSAP; no CMS. Content lives in JSON files and the generator prints the site from them — so a content change goes through a file, not a panel, and so does its version history.
-
Can I update the content myself afterwards?
Yes. Text and image sources sit in plain files; making a change and running the generator is one command. If you have no developer, an update retainer can be added — but you are never tied to a locked panel.
-
Who owns the site after handover?
All code and content sources are transferred to you; you are not tied to a locked panel or a subscription. The handover package includes repository access, setup notes and the measurement tools.