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

CMS for Istanbul businesses

How many ways into a platform there are is not something a home page shows. Readers often arrive with one question, and the answer to it rarely sits on the front page. On Tahlil.com we settled that on the content side: the tahlilmatik calculators stand as a separate published surface, so a person enters a single value and reads which reference range the result falls in, without booking anything first.

Get a quote Tell us about your project

CMS — Istanbul

In Istanbul what decides the shape of the work is not a single sector but the scale of the publication. As a publication grows, readers arriving behind one narrow question rather than through the front door becomes the normal case. The work closest to that condition is Tahlil.com. Where it does not overlap: it was written for health technology, and we have nothing to show on a corporate newsroom or a product catalogue. What carries across is not the subject but how many surfaces a publication opens from. The physician panel produces the final published text — a machine pre-read is prepared, the physician writes and approves it there. Laravel runs it, Tailwind shapes the interfaces, and React Native (Expo) with OneSignal covers the phone side; MySQL holds the records and Redis the cache.

  • The tahlilmatik calculators are a published surface of their own: a person enters one value, reads which reference range the result falls in, and reaches the platform without an appointment.
  • The final text a patient reads leaves the physician's hand — a machine pre-read is prepared, the physician writes and approves it in the panel, and nothing unapproved publishes.
  • The website, the physician panel and the mobile app hang off one Laravel application, so no second data model was written per surface, and OneSignal pushes a notification once a comment is ready.

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

Tahlil.com — a calculator page as an appointment-free surface, published on approval

A patient enters a test value; a specialist physician writes the reading. The home page is not the only way in: the tahlilmatik calculators are a surface of their own, where someone enters one value, sees which reference range it falls in, and reaches the platform without an appointment. In the panel a machine pre-read is prepared and the physician writes and approves the comment, so the last version a patient reads leaves the physician who signed it. The site, panel and React Native (Expo) app share one Laravel application. Newsrooms and catalogues sit outside the scope.

Read the case study →

Working with Istanbul 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 you have an office in Istanbul, and how would you work with our content team?

    We have no office anywhere and the work runs remotely. On the content side the work is writing down together which information gets published on which surface. On Tahlil.com we do not run the publishing; the physicians in the panel do. Your team keeps that decision, and we build the rules the panel enforces.

  • Why a custom build instead of an off-the-shelf content package?

    A package solves making pages; it does not solve how many surfaces you have. On Tahlil.com the second surface is a calculator, and someone enters it with one value. A surface like that is not picked from a plugin list — it comes out of the data model.

  • Who carries responsibility for text once it is published?

    The person who approves it. On Tahlil.com a machine prepares the pre-read, but publishing is the physician's decision. The panel holds that split: draft and approved text are two states on one record, and an unapproved comment never reaches the patient.

  • We want a mobile app alongside the site. Does content get entered twice?

    No. On Tahlil.com the site, the physician panel and the app hang off one Laravel application, and the app keeps no copy of the content. The mobile side is React Native (Expo), and OneSignal notifies the patient when a comment is ready.

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