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

CMS for Ankara businesses

A printed card leaves the building and cannot be called back; it circulates in someone's wallet for years. Inside a multi-unit institution the title, the extension and the unit name move faster than the card. QRVizit is the product we are building against that gap: the address a printed code points to is fixed once, and the page behind it stays rewritable from the panel. That is where CMS development in Ankara starts for us: with the part of a released object that can still be edited.

Get a quote Tell us about your project

CMS — Ankara

Ankara is dense with corporate head offices: one head office, a few units beneath it, each with a face turned outward. Printed material freezes the org chart while the chart itself keeps moving. The work closest to that condition is QRVizit — our own product, in build, with no version anyone can install today. Where it does not overlap: we have nothing to show on a corporate newsroom, a document archive or a multi-unit approval flow, and we run no public tender work. What we can describe is the arrangement: the admin panel and the visitor page live in one Laravel application, Inertia feeds the React interface, and Redis caches the page content while MySQL holds the records.

  • We fix the address a code points to once, so when a title or a unit changes, what gets rewritten is the content on that page rather than the printed object.
  • Nobody scanning a code downloads anything — the phone camera opens the page directly, and we build that page with Tailwind to be read on a small screen.
  • The admin panel and the visitor page live in one Laravel application with Inertia feeding React, so changing content never leaves a second service waiting to be updated.

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

QRVizit — the product we are building: a fixed code, a page written in the panel

This is our own product and we are building it now; there is no finished system and no version to install today. The arrangement: the address a printed code points to is fixed once, and the page behind it is rewritten from the panel as often as needed. Nobody scanning the code installs an app — the camera opens the page, and we build it with Tailwind to be read on a phone. The admin panel and the visitor page sit in one Laravel application, Inertia feeds React, and no separate service layer is set up. Redis caches the page content while MySQL holds the records. Scope: one profile page; newsrooms and document archives fall outside.

Read the case study →

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

  • Could you come to our head office and present this?

    We could not. We keep no office and work fully remotely, and that is the working model rather than a gap in it. What gets set up is a content model, not equipment handed over to the institution.

  • Can we install QRVizit today?

    No. We are building the product now and there is no version to install today. We say so plainly, because showing something as finished is how dates get missed later. What we can share is the arrangement and the ground it stands on.

  • Who writes the page content — does it come back to a developer?

    The institution writes it in the panel. Because the content fields are defined separately, correcting an extension number does not wait on a release from us. Had the page been one design file, every correction would go back through design.

  • If one code is scanned by a lot of people, does the page slow down?

    The cache carries that load. Page content is held in Redis, so every scan does not reach MySQL; the records stay in MySQL and the cache refreshes only when the content changes.

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