The pieces and their boundaries are settled before code.
Several institutions, one system, records kept apart.
One codebase, both stores: iOS and Android.
We take a running system over and improve it.
AI only where the problem actually calls for it.
CMS
A new page type, lesson, product or announcement goes live without waiting for a release. Who can see what, and who is allowed to change it, is defined alongside the content model.
A custom CMS is a content platform where your own team defines the content types instead of queueing behind a developer. Who gets to define a new type, and who is allowed to see or change each piece of information, is settled while the content model is drawn. Vipkurum lets its institutions define their own assessment standards, and Çatalca Merkez Kasap moved a printed menu onto one page.
The real question in content management is not what the writing screen looks like. It is who defines a new content type when one is needed, and if the answer is your own team, your publishing pace stops depending on a developer’s calendar.
At Vipkurum that right belongs to the institutions. Each one builds its own lesson, test, question and exam, and because the assessment type is not buried in code, a European standard and a Turkish one sit side by side on the same foundation. A teacher, a student, a parent and an administrator all read the same lesson programme at their own level of permission.
Çatalca Merkez Kasap had a different knot. While the information lived on paper, every price change meant another print run. Once the menu lives as text, a price change updates only the page and the printed code stays exactly where it is. The menu is split into sections, each with its own address, so codes on different tables or windows land on different points of one page. Nobody asked for a big system here: there is no ordering, payment or stock layer behind it. The wider pattern is in replacing printed catalogues with software.
QRVizit, still under development, applies the same split to a business card. The address a printed code points to stays fixed while the page behind it changes from a panel, and a change saved there reaches the visitor’s page with no transfer step in between.
All three carry one decision: the organisation defines the content type, and a change goes neither into a release queue nor to the printer.
Content management scope gathers around these areas:
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 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.
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.
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.
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.
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.
Every project goes through the same four stages: planning, architecture, modelling, development.
See our process
Seven education providers work inside one platform, each signing in at its own domain and appearing under its own name. Timetables, exams, students, guardians, payments and reporting all live in the same place.
Our own product, still in development. The QR code printed on a card points at one fixed address, while the page behind it is edited from a panel. When a number, a job title or an address changes, the record is updated and the box of cards stays valid.
A single-page QR menu. The menu splits into sections and every section carries its own address, so the code on a table and the code in the window open the page at different points. Built with Vue 3, moving between sections costs no new page request. No ordering, payment or stock layer.
Moving a catalogue or menu from print to software is not a file upload. We show how paper's job survives the move: opening instantly, installing nothing, asking the reader for nothing.
Seven separate installs, or one core? When the tenant boundary is a property of the data rather than a UI filter, adding an institution becomes a record instead of a deployment. Vipkurum shows how.
One scent ships in several sizes, one car in several trims, every used machine is one of a kind. Four live catalogues answer the same question differently: which record holds price and stock?
We write our own, and it lives inside the application itself. When you need a new content type you are not waiting for a plugin to permit it; the type is defined in the model and the right to define it stays with your team. Vipkurum lets an institution define its own assessment standard. The first conversation is where we work out which types you should own.
They can, and everything the model defines they change without asking us. The limit is not somebody's technical skill but how much room the content model leaves them. Vipkurum's institutions build their own exams and set their own standards, so a new one never waits on a code change. When you need a type the model does not know yet, you talk to us and we add it together.
It does not; the address a printed code points to stays fixed while the page behind it changes from the panel. A price, a phone number or an address can be updated without a print run on your side. Çatalca Merkez Kasap keeps its menu as text, so a price change updates only the page. In planning we work out which parts of your printed material actually change.
We can, and the first job is deciding how your content splits in the new model. Which type your own team will define, and which information stays inside whose permission; content moved before those answers carries its old problem into the new system. Çatalca Merkez Kasap moved a printed menu onto a page section by section, and each section got its own address. If you already run a working system, our evidence for taking one over sits on the software consulting page.