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 · Pendik

CMS for Pendik businesses

Someone standing at a machine reads a phone without taking a glove off, and one extra tap costs. When the signal thins inside the building, every jump between sections becomes another wait. For a multi-site service organisation or a manufacturer in Pendik the measure of a content system is not how rich the panel is but how many times the document has to open. For a butcher's shop in Catalca we answered that with a single page: moving between sections opens no new request.

Get a quote Tell us about your project

CMS — Pendik

Manufacturers and service organisations working across several points sit side by side in Pendik, and both hit the same thing: one document read from different service points. Our evidence comes from food retail — the menu written for Merkez Kasap in Catalca. For a production catalogue, technical service documentation or a spare parts list we have nothing to show; what travels is how the content is addressed. The menu was split into sections and each section carries its own address, so codes posted in separate spots land at different points in the same page. The stack shrank to the size of the job: Node.js and Vue 3, with no ordering, payment or stock layer. The page opens once; everything after that happens on the client.

  • The document downloads once, and because moving between sections opens no further request, a thin connection is not paid for again and again.
  • Every section carries its own address, so a code posted at one point drops the reader straight into that section instead of the top of the page.
  • Send someone the link to a section and they arrive at the same point, which removes the step of describing over the phone which heading to look for.

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

Merkez Kasap in Catalca — one page, section changes open no new request

A single-page QR menu written for a butcher's shop in Catalca, and the smallest build in our portfolio. The menu was split into sections and each section carries its own address, so codes posted in different spots land at different points in the same page. Because it is one page on Vue 3, moving between sections after the first load opens no further request, and a thin connection is paid for once at the door. Share the link to a section and the other side arrives at the same point. The scope was kept narrow: no ordering, payment or stock layer, and nothing that delays the first load.

Read the case study →

Working with Pendik 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

  • Do we need a separate page for every service point in Pendik?

    No. There is one document; the addresses are what differ. Each section carries its own address, so codes posted at separate points land at different places in the same page. One thing to maintain, not a set of copies.

  • The signal is weak on the production floor. Will the page open there?

    The wait is limited to one load. The page comes down once, and after that moving between sections opens no further request. A thin connection is paid for at the door, not on every tap.

  • What does a butcher's menu have to do with our technical content?

    Nothing by sector, something by shape. The Catalca build was written for food retail, and for a production catalogue or service documentation we have nothing to show. What travels is content addressed section by section and held on one page.

  • How do you set up the content without seeing the sites in person?

    We keep no office and work fully remotely. What we set up is a content model: which section gets its own address and which code lands where, written down. Standing on the floor is not what decides that.

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