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

CMS for Uskudar businesses

A sheet pinned to the noticeboard by an institution's entrance is doing two jobs at once: it is today's information, and it is the only proof the thing happened. So nobody takes the old sheet down; a new one goes over it. The announcements page of a clinic or a course centre in Uskudar can end up the same way. Günlük Hava Durumu untangles that by separating content types: what refreshes, what freezes once its date passes, and what is computed from the frozen rows.

Get a quote Tell us about your project

CMS — Uskudar

Uskudar is dense with health, education and appointment-run service organisations that publish notices, timetables and end-of-term information on a rhythm. The pinch comes from running everything as one content type: an expired notice cannot be deleted, because deleting it also removes the proof that the term existed. The work closest to that pattern is Günlük Hava Durumu. Where it does not reach is clear: it was written for weather and climate data, and we have nothing to show for patient records, appointment books, student files or institutional administration. What travels is the split by lifetime. Laravel produces the pages, MySQL holds the day records, React carries the interface transitions and Tailwind shapes them.

  • Content is split three ways by lifetime: the value that refreshes and is overwritten, the row that is written once when its date passes and never moves again, and the summary computed from those rows.
  • The summary comes from no second data source and is not typed by hand, so as the archive grows it renews itself.
  • The scope stays with weather and climate data — a chain built around a 15 day forecast stream — and patient or student records sit outside it.

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

Günlük Hava Durumu — three content types on one chain, with the summary computed

On a site publishing weather and climate data, content is split into three types by lifetime, and the three are links in one chain. The 15 day forecast stream refreshes, and the value on show is overwritten at the next update. Once a day's date passes, the record hands over to the archive side: written once and never altered again. The climate summary comes from no separate source: it is computed from those archived day records, and renews itself as the archive grows. Laravel produces the pages, MySQL holds the day records, and React carries the interface transitions.

Read the case study →

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

  • Our announcements page fills up with old items. How do we keep it clean without deleting them?

    Deleting is not the answer; separating types is. Today's information is content that refreshes, and once its date passes the same row hands over to the archive side and stops changing. When one sheet is no longer doing two jobs, the notice list gets short again.

  • Does the end-of-term summary have to be written by hand each time?

    That is exactly what the arrangement avoids. The summary comes from no separate source; it is computed from the frozen records. A hand-written summary falls behind as the archive grows, whereas a computed one keeps up with it.

  • We run a clinic, or a course centre. What does a weather site say to us?

    Nothing about weather, everything about how long a piece of content lives. The work we have was written for weather and climate data; patient records, treatment plans, student files and institutional administration are not things we can show. What carries across is deciding which content refreshes, which freezes and which is computed.

  • Did you work with a school or another institution in Uskudar?

    No. We claim no client in this district, we keep no office, and we work fully remotely. Günlük Hava Durumu sits here for its record shape: what gets published and what lands in the archive have different lifetimes. Your noticeboard splits the same way.

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