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

CMS for Izmir businesses

A link sent with a quotation is not always opened the day it is sent. The buyer opens the file weeks later, and what waits is either the promised page or a list whose address moved during a redesign. If you sell into export markets and the correspondence stretches over weeks, that risk grows. On Günlük Hava Durumu we closed it at the address: every date and location breakdown is published at a permanent address of its own.

Get a quote Tell us about your project

CMS — Izmir

Production and retail in Izmir work toward export, so a buyer judges the product from a distance and the correspondence stretches over weeks. In that setting a published page is worth as much as its address is stable, not only as much as its text is good. The work closest to that condition is Günlük Hava Durumu. Where it does not overlap: it was written for weather and climate data, and we have nothing to show on a product catalogue, a multilingual export site or customs paperwork. What carries across is not the subject but how a permanent address is produced per breakdown. Laravel renders the pages, MySQL holds the day records, React carries the transitions and Tailwind shapes them.

  • Every day at every location is published at a permanent address of its own, so a link sent with a quotation still lands in the same place weeks later.
  • The live 15 day forecast refreshes and the value on screen is overwritten at the next update; once a date has passed, the record moves to the archive side while the address stays put.
  • When a new breakdown appears its address appears with it, so nobody opens pages by hand and the page structure is not redrawn to fit.

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 — every date and location breakdown at its own permanent address

A platform for weather and climate data. Its defining decision is the address: every day at every location publishes at its own permanent address, and it does not move afterwards. The live 15 day forecast refreshes and the displayed value is overwritten at the next update; once the date passes the record hands over to the archive, written once and never changed. A new breakdown brings its address with it, so no page is opened by hand. Laravel renders pages, MySQL holds day records, React carries transitions. Scope: weather and climate data; catalogues and export paperwork sit outside.

Read the case study →

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

  • If we rebuild our site, do the old links break?

    That is a decision the content model makes. On Günlük Hava Durumu the address is tied to the breakdown itself — a date and a location. Had it been tied to a position in a list, it would have moved the moment the list did.

  • Who grows the content? Do we call you for every new page?

    You would not need to. On Günlük Hava Durumu no page is opened by hand: when a breakdown appears, its address appears with it. The publication deepens as the archive grows, without the page structure being drawn again.

  • Could you build a multilingual publication for export?

    We have nothing to show on a multilingual export site, and we say that as it is. What we can describe is the address side: giving a breakdown its own permanent address is the same decision you face again when a language is added.

  • Would you travel to Izmir for a meeting?

    We would not. There is no office to meet at and the work runs remotely throughout. On the content side what we need is not a visit but a written agreement on which breakdown deserves an address of its own.

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