# Web design and website development

We design and build your company website: a corporate site, service and product pages, a blog or a bilingual setup. Depending on the need, we build a custom-coded site or WordPress with a custom theme, and hand over written instructions for updating it.

[Tell us about your project](https://rufystudio.com/en/contact?service=web-design)

[All services](https://rufystudio.com/en/services)

Platform

React · TypeScript · Tailwind CSS · WordPress

Who it is for

## Who this service is for, and who it is not for

A good fit

- **Companies commissioning their first proper website**
  You know what you want to say, but there is no page structure, copy order or visual language yet. We build those with you, starting from the site map.
- **Teams whose site has aged or become unmanageable**
  A bought theme that got heavier with every plugin, a site that breaks on mobile, or one nobody can update. When we plan the new one, every old URL is 301-redirected to its new counterpart, and we monitor Search Console after the switch.
- **Teams taking a site over from an agency or freelancer**
  It is unclear who holds the access and the code is undocumented. We first map the current state, then recommend in writing whether to keep working on it or rebuild.
- **Companies publishing in Turkish and English**
  Each language gets its own URLs, its own page titles, and hreflang tags that tell search engines the two versions are counterparts. The site you are reading works this way.

Not a fit

- **A single page that has to be live within days**
  For an announcement or event page, a ready-made site builder is usually enough. If that is the request, we will tell you so.
- **Installing a ready-made theme and nothing more**
  If the budget covers only pouring content into a bought theme, many services do exactly that. Our work is building the structure and design around your content.

Platform

## Custom-coded site, WordPress or an e-commerce platform

We choose the platform before design starts, because who updates the content, and how often, changes the answer. The proposal says which one we recommend and why.

- **Custom-coded site**
  React · TypeScript · Tailwind CSS · Vite
  When
  When the number of pages is known, content changes rarely, and speed, security and a low maintenance load come first. Pages are turned into static HTML before publishing; no database or plugins run on the server, so there is no plugin list to keep updated. This site was built this way.
  The trade-off
  Content changes go through the code. If your team will update content itself, we recommend WordPress or a separate content panel connected to the site.
- **WordPress, custom theme**
  WordPress · PHP
  When
  When someone on your team will add news, blog posts, team and reference pages themselves. We do not use bought themes; we write the theme to the design and define each editable field in the admin panel, so entering content does not break the layout.
  The trade-off
  WordPress core, the theme and plugins need regular updates. Who does that maintenance is agreed in writing before handover.
- **E-commerce platform**
  When
  When the site’s main job is selling and you need product, stock, payment and shipping management. We do this as a separate service: the choice between WooCommerce, Shopify, a Turkish platform or a custom-coded store, and the payment and shipping integration, are described on our e-commerce website page.
  The trade-off
  On ready-made platforms, the platform’s rules and monthly fees come with the project. Which platform fits depends on your number of products, the flows you need and who will run the store.

Deliverables

## What you receive at the end of the project

### Planning

4 items

1. Site map: page list and hierarchy
2. Content plan per page: heading, sections, who writes the copy
3. Inventory of old URLs and a redirect map (for redesigns)
4. List of events to track: form submissions, phone and email clicks

### Design

4 items

1. Desktop and mobile page designs
2. Component library: button, card, form, heading and list styles
3. Colour, typeface and spacing rules
4. Source design files

### Development

6 items

1. The live site and a staging URL
2. The complete source code, in a Git repository on your account
3. Title, description and share image for every page
4. sitemap.xml, robots.txt and structured data
5. 301 redirects from old URLs
6. Form notifications and analytics events

### Handover

4 items

1. Account and access list
2. Written user guide
3. CMS training session (on WordPress projects)
4. Launch-day checklist

Process

## The process, step by step, and what each step produces

Every step ends with a concrete output for your approval. We move on once that output is approved.

1. **Discovery**
   We discuss what the site needs to do, who it needs to reach and the constraints we are working within. If there is an existing site, we list its pages, which of them get search traffic and which have links from other sites.
   Output
   Scope document and draft site map
2. **Content and structure**
   We decide what each page says, in what order and in which sections. Who writes the copy is settled here. We design with real content, not placeholder text.
   Output
   Content plan per page and wireframes
3. **Design**
   We first present the home page and one inner page for your approval. Once the direction is approved, we complete the remaining pages and the mobile views in the same language.
   Output
   Approved page designs and component library
4. **Development**
   We build the site on a staging URL, where you can follow progress too. Forms, analytics events, page titles and structured data are added at this step.
   Output
   Working site on a staging URL
5. **Testing and launch**
   We check across browsers and phones: do the forms actually send email, do the redirects work, are the pages open to search engines. We launch at the hour with the least traffic.
   Output
   Live site and a completed checklist
6. **Handover**
   We hand over accounts, access and documents. On WordPress projects we run a training session with the people who will enter content.
   Output
   Handover pack: access list, guide and source code

Risks

## Common problems in website projects and how we prevent them

- **Content arriving late and the project dragging on**
  Waiting for copy and images delays schedules more than anything else. The content plan names an owner and a due date for every page; a missing page does not stop the design, it only holds back that page’s launch.
- **WordPress slowed down by a pile of plugins**
  Installing a new plugin for every need slows the site and adds parts that need updating. We write design-related features into the theme and use plugins only for well-understood jobs such as forms and backups.
- **Nothing being measurable after launch**
  Without knowing which form was sent and when, there is no way to tell whether the site works. We write the list of events to track during discovery and test each one on launch day.

Example

## Live examples of this work

- **[Hermosa Concept](https://rufystudio.com/en/work/hermosa-concept)**
  A WordPress-based catalogue site for a furniture company: four product categories, product pages with prices and dimensions, project pages and contact via WhatsApp.
  Website · Furniture
  [hermosaconcept.com](https://www.hermosaconcept.com)
- **[Carnot](https://rufystudio.com/en/work/carnot)**
  A site for a manufacturer of industrial cooling machines, made up of product, sector and service pages, together with the SEO content on those pages.
  Website · Industrial cooling
  [carnotindustrial.com](https://carnotindustrial.com)

- **[rufystudio.com](https://rufystudio.com/en)**
  The site you are reading: a custom-coded, bilingual Turkish and English site written with React, TypeScript, Tailwind CSS and Vite. What was done on the search side is described on our SEO service page.

Cost

## What determines the cost of a website

- **Number of distinct page layouts**: Cost depends less on the number of pages than on how many of them have a different layout. Many service pages sharing one layout can be less work than a handful of pages that each look different.
- **Who prepares the content**: If copy and images come from you ready to use, the work stays within design and development. Copywriting, photography and illustration are separate line items.
- **Choice of platform**: A custom-coded site, custom-theme WordPress and an e-commerce platform bring different work items and a different maintenance load.
- **Integrations**: Exchanging data with a CRM, a booking system, an ERP or another service. Each integration means its own tests and its own failure cases.
- **Number of languages**: Each additional language means translation, separate URLs, hreflang tags, and a title and description for every page in that language.
- **Migrating from an existing site**: Moving old content across and preparing the redirect map is a work item in its own right, scaled to the size of the old site.

Once the scope is agreed in writing, we prepare an itemised proposal. Which post-launch support tasks are covered, and for how long, is stated separately in the proposal.

[Request a proposal](https://rufystudio.com/en/contact?service=web-design)

Ownership & handover

## Who keeps the domain, hosting, code and accounts

When the project ends, everything about the site is under your control.

Handover list

- **Domain**: Registered in your name, on your account. If you already have a domain, we do not transfer it; we only ask for access to change its DNS records.
- **Hosting**: The hosting account is opened in your name and billed to you. We choose the provider together, and we are added to the account as an authorised user.
- **Source code and design files**: The full code is transferred to your account along with its Git repository, and the design files are handed over. There is no licence or lock that stops you continuing with another developer.
- **Analytics and search accounts**: Google Analytics, Search Console and Tag Manager are opened with your company account. We are users on them, not owners.
- **Training and documentation**: We hand over a written guide explaining how to update the site. On WordPress projects we run a training session with the people who will enter content.

FAQ

## Questions people ask before commissioning a website

[Ask your question](https://rufystudio.com/en/contact?service=web-design)

### What does the cost of a website depend on?

Mostly on the number of distinct page layouts, who prepares the content and the choice of platform. The other factors are listed in the cost section on this page; once the scope is agreed in writing we give an itemised proposal.

### How long does a website project take, and what makes it longer?

Duration depends most on whether the content is ready, the number of approval rounds and integrations. Projects usually run long because copy and images are awaited, the decision-maker joins late, or the scope grows after design is finished. With the proposal we give a step-by-step schedule that also states what is needed from you at each step.

### Who owns the domain, hosting and source code?

You do. The domain and hosting are registered in your name, and the complete source code and design files are handed over. We are added to the accounts only as authorised users; when the work is done, you can remove our access.

### Can you take over or redesign our existing site?

Yes. We first review the current site and map the state of access, code and content. Then we recommend in writing whether it makes more sense to keep working on the site or to rebuild it.

### What happens to our Google rankings and content when we move to a new site?

Every old URL is 301-redirected to its new counterpart, and the content of pages that bring traffic is either carried over as it is or deliberately updated. Rankings can fluctuate for a while after the switch. The search side of a migration is covered in detail on our SEO service page.

### Ready-made theme or custom design?

A ready-made theme starts faster, but all of its features and plugins come with your site. Code you do not use slows pages down, and the design stays within the theme’s limits. Even on WordPress projects we do not use bought themes; we write the theme to the design. If your budget only covers a ready-made theme, we will say so plainly.

### Do you write the copy?

We plan the page structure and what each section says. Your team can write the copy, or we can add copywriting to the scope. Either way, it appears as a separate line in the proposal.

### What happens after the site goes live?

After launch, for the period written in the proposal, we monitor the forms, redirects and Search Console reports and fix the bugs that come up. Later maintenance, updates and new pages are written into the proposal as separate items.

Related services

## Often considered alongside this service

- **[E-commerce website](https://rufystudio.com/en/services/e-commerce-website)**
  Sites that sell products. We choose the platform to fit the job: WooCommerce, Shopify, a Turkish platform such as ikas, or a custom-coded store. On the payment side we set up iyzico, PayTR or your bank’s virtual POS with instalments; on the shipping side, shipment creation and tracking.
  WooCommerce · Shopify · iyzico · PayTR
- **[SEO](https://rufystudio.com/en/services/seo)**
  We work out which searches your site should appear for, and with which page. Technical SEO fixes crawling and indexing problems; we plan and write the pages that are missing.
  Search Console · Google Analytics · Schema.org
- **[Google Ads & Meta ads](https://rufystudio.com/en/services/google-ads-meta-ads)**
  We set up and run Google search ads and Facebook and Instagram ads. Before any budget is spent, we define which actions count as conversions and set up their tracking.
  Google Ads · Meta Ads · Google Analytics
- **[Mobile app development](https://rufystudio.com/en/services/mobile-app-development)**
  iOS and Android apps. Depending on the project we use Kotlin Multiplatform or React Native, so the part both platforms share is written once. Santra and Aera Wallet, which we built and released, are on the App Store and Google Play.
  Kotlin Multiplatform · React Native · iOS · Android

Rufy Studio

## Tell us about your site, or the one you want to build

Send us your current site’s address, if you have one, and what you want to change; our platform recommendation starts from there.

[Tell us about your project](https://rufystudio.com/en/contact?service=web-design)

---
Source: https://rufystudio.com/en/services/web-design-development
