Add the feature you need without rebuilding your site.

Adding a new language and a custom module to an existing site

Custom module development means adding a new feature to a working website without rebuilding the whole site. A multilingual structure, an appointment system, a quote calculator, a member area or data exchange with other software are the most common requests in this scope.

This service is for companies that are generally happy with their site's design and content but have a new need as their business grows. If you have no site at all or yours is completely outdated, corporate web design is the better starting point; if you need a system to manage all your business processes, our custom software service is.

Module or new site?

The infrastructure of the site decides this. Adding a module to a site running on an up-to-date, maintained content management system usually makes sense. On the other hand, adding a new feature to an infrastructure that has not been updated for years and is no longer supported, or to a site whose source code is unclear, can magnify security and compatibility problems. In the review we look at these questions:

• Are the site's core software, theme and plugins up to date?
• Does the hosting environment meet the version and resources the module requires?
• Do you hold the administrator access and the domain?
• Is there a ready-made, reliable and maintained solution that does the same job?

If a ready-made solution meets the need, we do not recommend writing code from scratch; installation, configuration and adaptation are often enough. Custom development comes in when ready-made options do not fit your business rule or make the site needlessly heavy.

How should a multilingual website be built?

A multilingual structure is not just adding a translate button to a page. For search engines to understand each language separately, each language version must have its own address; for example, a subfolder or subdomain structure should be used. The language relationship between pages is stated with hreflang tags, so that a user searching in German can be shown the German page. The menu, forms, error messages, email notifications and legal texts must also be translated; translating only the main texts and leaving the form in Turkish leaves the visitor stranded halfway.

We recommend that translations be prepared or checked by someone who knows the language or by a professional translator. Automatic translation can be used for a draft, but mistakes in industry terms and product names damage trust in the eyes of a foreign customer. We set up a structure in the panel where you can update the content of each language separately. Adapting details such as currency, date format, phone field and address format to the target country is also necessary so that a foreign visitor can fill in the form without trouble.

Appointment, quote and calculation modules

Modules of this kind let the visitor take the next step without leaving the site. In an appointment module, working hours, service durations, holidays and conflict checking are defined; when a request arrives, a notification goes to you and to the visitor. In quote or calculation tools, an estimated amount or an orderly quote request is produced based on options such as measurements, quantity and materials. What matters here is that the calculation rules are clearly defined by you and that it is clearly stated that the result shown is not binding. In every module that collects personal data through a form, there is a link to the KVKK privacy notice and a clear consent box.

Integrations and data security

Passing information from the forms on your site to a CRM, an email marketing tool, accounting or reservation software removes manual data entry. We set up these connections with the official API or integration methods offered by the relevant system. Access keys are not kept in the site's public code; permissions are defined with the narrowest possible scope. Instead of sharing your passwords, we ask you to define a separate authorized user for us in the systems you use. In case an integration stops working one day, we also set up error notification and a backup record mechanism so that records that could not be transferred are not lost.

How is it added to the live site?

1. A file and database backup of the site is taken and a restore point is created.
2. A test copy closed to visitors is prepared.
3. The module is developed on this copy; its compatibility with existing pages, its mobile view and its effect on speed are tested.
4. You check the test address and give your approval.
5. The change is put live at a time of low traffic, and afterwards forms, payment or notifications are tried again.

With companies in Sakarya and around, we can discuss the need on site and explain the module face to face to the people who will use it. Projects across Turkey run online; the same steps are followed with a test address and screen sharing.

Common mistakes

• Installing several plugins that do the same job: Similar plugins conflict, slow the site down and increase the risk of security holes.
• Updating without a backup: If a module update goes wrong, there is no point to return to.
• Leaving the translation half done: A site whose home page is in English and whose contact form is in Turkish does not build trust with a foreign visitor.
• Leaving the module without an owner: If it is not decided who will update the added feature and how often, it breaks over time.
• Not measuring speed: Every new feature adds code to the page. Comparing speed measurements before and after the module is the simplest way to make sure the site's Core Web Vitals values have not declined.