Get a quote

CMS · Sariyer

CMS for Sariyer businesses

When the archive is bound, the content exists but has no address: to use one page of a booklet on its own you have to break the spine. For training units on Sariyer's Maslak tower floors and publishing teams around the Ayazaga campus that is a familiar wall. A content system goes in, the old archive goes in with it as a PDF attachment, and the system ends up holding files rather than content. The tool we wrote for Vipkurum turns a booklet already in hand into a pool split question by question.

CMS — Sariyer

Sariyer holds technology and head office floors alongside a university belt. Where content was produced once and cannot be used again, the problem is not the size of the archive but what its smallest unit is. The work closest to that profile is the question cropping tool we wrote for Vipkurum, built in an education technology context. Corporate document management, contract archives and financial content are outside it; what we describe is a printed source becoming records. A booklet page is divided into single questions by OpenCV, each question is tied to its entry in the answer key, and the key stops being a separate document. Cropped images and question records sit in MongoDB, and the Python image processing service connects through Node.js to the content management side in Laravel.

  • Printed material enters the system as individually addressable records rather than as an attachment, so each piece can be found and reused on its own.
  • The answer key stops being a separate document and is written into the question's own record, which removes the step of holding two files side by side.
  • Gaps in the pool are filled from questions already in hand: the model writes a new one in the same form, together with its answer key.

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

Vipkurum question cropping — a bound booklet becomes an addressable pool

A tool written in an education technology context. OpenCV divides a booklet page into single questions, so printed material already in hand becomes a pool in which every piece is its own record. The answer key stops being a separate document and is written into the cropped question's record. Questions that are missing get written from existing examples together with their answer key. Cropped images and question records sit in MongoDB, and the Python image processing service connects through Node.js to content management in Laravel. The scope is education content; for a corporate document archive we have nothing to show.

Read the case study →

Working with Sariyer 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 archive is a set of PDFs. Can we not just upload them?

    You can, but then the system holds files rather than content. If you want a piece that can be searched, quoted and reused on its own, the smallest unit of the record has to be that piece and not the page. In Vipkurum that unit is a single question.

  • How does the pool grow, and what about material we do not have?

    Questions already in hand are used as examples, and the language model writes new ones in the same form together with their answer key. New content comes out of the archive's own shape rather than from outside it.

  • The material is at our campus unit in Sariyer. Do we have to bring it to you?

    No, and there is nowhere to bring it: we keep no office and work fully remotely. A printed source becomes a file the moment it is scanned, and everything after that happens on the image processing and record side.

  • Our content is not training material. What does this build say to us?

    Vipkurum was built in an education technology context and we say so plainly. For corporate document management or a contract archive we have nothing to show. The one thing it says is this: a printed source in hand can enter a system as records instead of as a file.

Let's talk about who will manage your content.