work details

GZL Technology — Corporate Sales and Portfolio Platform

A multilingual corporate platform presenting GZL Technology services, SaaS products, project evidence, editorial content and structured quotation workflows.

Client

GZL Technology

Start

11 Jun 2026

Completed

GZL Technology — Corporate Sales and Portfolio Platform interface and project preview
Description

A multilingual corporate platform presenting GZL Technology services, SaaS products, project evidence, editorial content and structured quotation workflows.

Case study

Challenge

Two legally separate companies run by the same team needed websites, without writing and maintaining two codebases. With a single codebase, one brand's name, contact details or legal name must never leak onto the other brand's pages.

Approach

We kept the schema shared and the content separate: seed files are classified, brand data is generated at build time from each installation's own API, and a rule prevents missing values from being filled from the other brand. Releases are built locally, separately per installation, with health checks and automatic rollback.

Outcome

gzlteknoloji.com is live in three languages with translated URLs, and services, packages, products, portfolio and blog are managed through the panel. The same codebase also powers the Guezel Web Design site with its own database.

Tools

Next.js, React, TypeScript, Fastify, Drizzle ORM, MySQL, Bun

Key Features
  • One codebase, two brands: separate databases and builds

  • TR/EN/DE content with translated URLs (/hizmetler, /leistungen)

  • 22 services, packages and a SaaS product showcase

  • Quote form pre-filled with the selected package code

  • Portfolio case studies in problem–approach–result format

  • Admin panel with 30+ content and settings screens

  • Key-protected, trilingual content API for Tanitio

  • Local builds, health checks and automatic rollback

  • Visible legal notice and per-installation llms.txt

Technologies Used
  • Next.js

  • React

  • TypeScript

  • Fastify

  • Drizzle ORM

  • MySQL

  • Bun

Design Highlights
  • Missing brand data is never filled from the other brand; it stays empty

  • One canonical URL per page, with hreflang and x-default

  • WebP-only images and 1600×900 covers, sized for a single-core server

  • A build check that blocks release when a translation is missing

  • GA4/GTM measurement tied to cookie consent (Consent Mode)

Details

gzlteknoloji.com is the corporate sales and portfolio website of GZL Teknoloji Ltd. Şti. It presents software services, ready-made packages, the company's own SaaS products, delivered projects and blog content on a single manageable platform. The target audience is businesses looking for a corporate website, e-commerce, custom ERP/CRM or AI search optimisation. The site is also a live example of the agency's technical approach: the same codebase runs two separate brands with separate databases.

Context and need

GZL Teknoloji and Guezel Web Design in Germany are run by the same team but are two legally separate businesses. Both needed to manage services, packages, products, a portfolio and a blog. Instead of writing and maintaining two separate codebases, the goal was one codebase with two independent installations. The most critical requirement was brand separation: one brand's name, logo, phone number or legal name must never appear on the other brand's pages. The second need was a short sales path that lets visitors explore a service and move straight into a quote request.

Solution and scope

What visitors see

  • Home page: brand banner, core services, three featured products, selected projects and a contact block.
  • Services: a list with category filters and a detail page for each service that also shows related projects. 22 services are defined, including corporate websites, e-commerce, custom ERP, OSGB (occupational health and safety) management, AI search optimisation (GEO), GA4/GTM conversion tracking and B2B product catalogues.
  • Packages: e-commerce, social media and maintenance packages, plus monthly SaaS plans. The “get a quote” button pre-fills the contact form with the selected package code.
  • Products: Tanitio, TeklifRota, ERP, CRM and the OSGB system, with specifications, FAQs, demo and documentation links.
  • Portfolio: case studies structured as problem, approach and result, with links to related services.
  • Blog, corporate and legal pages: articles on GEO, AI recommendations, e-commerce costs and business process automation; legal notice, privacy and policy pages.

Three languages, translated URLs

The site is published in Turkish, English and German, with Turkish as the default on gzlteknoloji.com. Not only the content but also the URLs are translated: /tr/hizmetler, /de/leistungen and /en/services are the three addresses of the same page. All language segments are managed from a single mapping file; requests to the internal English route are permanently redirected to the translated address, so every page has exactly one canonical URL. A check that runs at build time stops the release if any service or project is missing a slug, name or summary in one of the three languages.

Admin panel

A separate Next.js admin panel manages services, packages and pricing, products, projects, the blog, corporate and legal pages, custom pages, FAQs, menu and footer sections, site settings, the media library, brand logos, skill counters, reviews, contact messages, newsletter subscribers, email templates, notifications, support tickets, users, roles and audit logs. Even the panel's own interface texts are stored in the database and can be edited.

Technical architecture

The front end uses Next.js 16, React 19 and next-intl; the panel uses Next.js 16, Tailwind CSS 4, TanStack Query and react-hook-form/Zod; the backend runs Fastify 5 on Bun with Drizzle ORM and MySQL. Most API modules come from a shared backend package used across several projects.

Two brands, one codebase

The schema is shared between the two installations; the content is separate. Every seed file is classified as “schema”, “core” or “brand content”; the GZL installation is built with its own content profile, and a check script fails if an unclassified file is found. Brand data is generated at build time from the installation's own API: logo, contact details, interface texts and legal name. A value missing from the database is never filled from the other brand; it is left empty. The registered company name, tax and registry details are printed as a visible legal notice on the site. llms.txt files are also generated separately for each installation.

SEO and performance

Each page takes its metadata, canonical URL and hreflang for three languages plus x-default from SEO settings in the database. Organization, WebSite, Article, BreadcrumbList, FAQPage and ProfessionalService structured data are used, and a dynamic sitemap lists services, projects, products and pages under their translated addresses. To limit optimisation load on the single-core server, images are served as WebP only; cover images were standardised to 1600×900, and project images previously hotlinked from a third-party CDN were moved to the site's own server. List and detail data are refreshed via ISR every 60 seconds, the sitemap every hour. Analytics run through GTM and GA4, tied to cookie consent via Google Consent Mode; security headers and HSTS are active in production.

Integrations

The backend provides a read-only content endpoint for the Tanitio marketing platform: blog posts, services and projects can be read in three languages, with pagination, search and filtering by update date, behind a constant-time key check. Tenant-specific texts come from site settings rather than code. The contact form, email templates and notifications run on shared modules.

Release process and today

Nothing is built on the server. The release script builds the main branch in a local worktree, separately for each installation with that installation's environment settings and API, so the same build output never goes to both sites. The output is transferred to the server, the current version is kept as a backup and swapped for the new one, and the process is restarted; if the front end, panel or backend health checks fail, the previous version is restored automatically. GitHub Actions runs lint, type checking and a build gate on every push. gzlteknoloji.com is live on this setup, with services, products, portfolio and blog content maintained through the panel.