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.
Platform
React · TypeScript · Tailwind CSS · WordPress
01Who it is for
A good fit
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.
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.
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.
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
For an announcement or event page, a ready-made site builder is usually enough. If that is the request, we will tell you so.
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.
02Platform
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 · 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.
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.
03Deliverables
04Process
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
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
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
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
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
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
05Risks
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.
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.
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.
06Example
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
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
07Cost
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.
08Ownership & handover
Handover list
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.
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.
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.
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.
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.
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.
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.
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.
Rufy Studio
Send us your current site’s address, if you have one, and what you want to change; our platform recommendation starts from there.