Ask ten business owners about WordPress and you will hear that it is either child's play or a security nightmare. Neither verdict is about the software. It is about the person who configured the installation and whoever is responsible for it a year later. One WordPress install lets a receptionist post a notice before her coffee cools; another has grown into thirty extensions that everyone is afraid to touch. Which of those you end up with is settled long before development starts. Imagine an İzmir law practice of eight lawyers. The partners want short commentary on new legislation, an English section for overseas clients and online booking for initial meetings. Put that on paper and the solution is modest: a theme made for this practice and a few carefully chosen, actively maintained extensions. Every addition beyond that has to earn its place in writing.
A WordPress build from Apply consists of the parts below. Anything outside this list needs a written reason before we install it.
We develop Gutenberg blocks for the content you actually publish: service cards, staff profiles, pricing grids, notices, downloadable documents. Editors combine them into new pages with no page-builder plugin, and phones still display everything properly.
Writers submit, a reviewer publishes, and plugin or theme settings belong to one or two people. It sounds bureaucratic, yet it is what stops an intern from switching off the cache on a busy Monday.
Turkish first, then English or Arabic through Polylang or WPML. Every language lives at its own address with matching hreflang markup, which keeps Google from showing a Turkish page to someone searching in English.
Each form carries a brief KVKK notice, the cookie policy has its own page, and analytics or YouTube embeds only load once a visitor opts in. Your legal adviser signs off the text; we build the mechanics.
Spam-resistant forms without annoying picture puzzles, and if you need it, appointment slots pulled live from Microsoft 365 or Google Calendar. Messages reach the person who handles them, not a forgotten generic inbox.
Mandatory two-step sign-in for administrators, throttled login attempts, server-side caching, images served as WebP, and nightly backups copied to separate storage.
Programming is seldom what slows a project. The real variables are the number of different page layouts and the date your texts arrive.
Colours can wait. In an online meeting we list what your people publish now and what they would like to publish: announcements, commentary, job adverts, events. That list defines the blocks.
The theme is built in a private test environment. You assemble a couple of genuine pages there on your own, and it becomes obvious very quickly whether the blocks fit your routine.
We import or re-enter existing copy, route forms to email or your CRM, pair up translations and prepare a redirect map from every old URL.
Switch-over with permanent redirects, all accounts transferred to the company, a short training session on Teams or Meet, and a single page describing the maintenance routine.
An expired premium plugin licence does not break your site. It simply stops the security patches. We see this constantly on small business sites: someone bought the forms or SEO add-on with a personal card, that person moved on, the renewal bounced and the plugin has been quietly ageing ever since. We therefore buy every licence in the company name against a shared mailbox such as info@, and list renewal dates in the handover document.
Written for you, deliberately without a bulky framework. Multi-purpose marketplace themes bundle hundreds of options; a typical site uses a fraction, and the unused remainder is still code that needs patching. A purpose-built block theme is smaller, faster and cheaper to keep healthy.
An audit decides. A light theme with up-to-date extensions can be modernised in stages. When the site is locked into a heavy builder or an unsupported commercial theme, starting a new theme is usually the cheaper route. Your copy, media and URLs survive in both scenarios.
Certainly. What matters is a supported PHP version, SSH access and dependable backups. Choosing between a Turkish and an EU data centre depends on your audience and on how you assess cross-border data transfers under KVKK. The hosting account belongs to your company; we can configure a fresh server or work with your current provider.
We prepare the theme so WooCommerce can slot in later. Installing a shop you do not use yet just creates more updates to manage, so we add it at the point you actually start selling.
It scales with page layouts, languages and integrations. Following the first meeting you get a phased quote. Changes requested after sign-off are charged at €55 per hour plus VAT.
A few lines on what visitors should be able to do and whether a site exists today are enough. Expect questions and a proposed meeting slot within one working day.
We have your enquiry
A reply will reach you by the next working day at the latest. If your message says work has come to a halt, it goes to the top of the pile.
No such city in our list. Try another spelling, or just pick the closest big city: we work entirely over remote connections, so nothing about the service changes from one province to the next.
The only cookies here are the essential ones: they keep the site running and remember the city you picked. Nothing is used for advertising or tracking. See our privacy notice for more.
