EN TR
Get a quote
View all services
Web software

One app carries the brochure pages and the request queue.

System architecture

The pieces and their boundaries are settled before code.

Enterprise & commercial software

Several institutions, one system, records kept apart.

Mobile app

One codebase, both stores: iOS and Android.

Software consulting

We take a running system over and improve it.

AI consulting

AI only where the problem actually calls for it.

Get a quote
EN TR

CMS · Kartal

CMS for Kartal businesses

The front office of a workshop can hold one computer with nobody at it all day. Whoever updates the site is also the one who picks up an incoming request, on the same screen. So a second admin panel is, in practice, a panel nobody opens. That is where the CMS question lands along Kartal's manufacturing strip: do the marketing pages and the incoming requests live in one application? In Diotek they do, and the requests still never share a queue.

Get a quote Tell us about your project

CMS — Kartal

Manufacturers line the main road through Kartal, and appointment-led service businesses sit around the health campus edge. Neither gets just one kind of request. The work closest to this district's sector profile is Diotek, written for an air conditioning and ventilation company. Production planning, shop floor records and the running of a health institution are outside it; what we describe is the moment a request lands on the site. There, a survey booking and a post-installation service call were built as two flows from the start, and both sit in the same Laravel application as the marketing pages. Laravel runs it with an Inertia interface, MySQL holds the records and Redis the cache, and content and request records sit on one schema.

  • The screen that edits the marketing pages and the screen where a request arrives open in the same session, so there is no second password for a separate system.
  • Sharing an application is not sharing a queue: a survey booking is a record attached to a place, a service call is a record attached to installed equipment.
  • Inertia handles page transitions on the client while validation stays in Laravel, and a Redis cache absorbs the start-of-season load inside the same code base.

Why Algoriel

  • Print becomes editable

    Çatalca Merkez Kasap moved a printed menu to a QR page, so a price change is an edit rather than a reprint.

  • Content gets an address

    Each menu section carries its own address, so a customer can link straight to the section they came for.

  • The institution authors

    Teachers on Vipkurum write their own lessons, tests and exams, so publishing does not wait on a developer.

  • Fixed code, editable page

    QRVizit fixes the printed address once; the page behind it stays editable. We are still building it.

What we build

CMS

  • Content modelling

    Which content types exist, and which fields each one carries, follows your own publishing work. At Vipkurum the assessment type is not hard-coded, so European and Turkish standards sit side by side on the same foundation.

  • The editorial interface

    The person writing and the visitor reading see the same information, with no second copy waiting to be synchronised. Keeping the admin panel and the published side in one application means the content is not held in two places.

  • Addresses and links

    Every page and every section carries a permanent address of its own, so a shared link always opens the same place. At Çatalca Merkez Kasap the menu is split into sections, and codes on different tables land on different points of the same page.

  • Access and permissions

    Who sees what, and who may change it, is defined together with the content type. At Vipkurum a teacher, a student, a parent and an administrator read the same lesson programme at their own level of permission.

  • An update is not a reprint

    When a price, a phone number or an address changes, the printed material stays as it is and the page is updated instead. Çatalca Merkez Kasap keeps its menu as text, so a price change never reaches the printer.

  • Repeat reads

    When the same page is opened again and again, it is served from a ready copy rather than rebuilt each time. QRVizit, still under development, opens a repeatedly scanned card that way.

Work like this

CMS · Case study

Diotek — content and requests in one Laravel app, queues kept apart

An air conditioning and ventilation company gets two things asked of its site: a survey booking for a space before any equipment is chosen, and a service call for maintenance or a fault after installation. They were built as separate flows from the start. Marketing pages, survey records and service records sit in one Laravel application on one MySQL schema; Inertia handles page transitions on the client while validation stays in Laravel, and a Redis cache absorbs start-of-season traffic. Sharing an application is not sharing a queue: requests reach operations already separated, and the record does not depend on a phone line.

Read the case study →

Working with Kartal teams, remotely

We have no office, so work for this city runs remotely and we do not offer on-site support. What was done, and why it was done that way, stays in writing. The project pages mark which builds came out of a partnership.

  • The first release ships as a working piece; extras follow later.
  • Every client we know of is in Turkey.
  • Decisions stay in writing; progress shows in working screens.

Frequently asked

  • We manage content in one program and incoming requests in another. What does merging buy us?

    One session. In Diotek the marketing pages and the request records live in the same Laravel application on the same MySQL schema, so there is no second password to keep and one surface to maintain instead of two.

  • If they merge, do all requests land in one list?

    No. Sharing an application is not sharing a queue. A survey booking is a record attached to a place; a service call is a record attached to installed equipment. Their fields differ and so does their order.

  • What happens to a request that arrives while nobody is at the screen?

    It lands in writing and stays there. That is the point of opening a request from the site: an entry that does not depend on anyone remembering. A request that comes in after hours opens the same record.

  • Diotek is an air conditioning company and we manufacture on Kartal's manufacturing strip. What does it say to us?

    Not the sector, the shape of intake. If more than one kind of request reaches your site, the split belongs at the door rather than on the phone. Rename the container and the split stays where it is.

CMS in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

Let's talk about who will manage your content.

Get a quote or open the service