Every website we build runs on our own CMS. It keeps the languages in step and converts images automatically. It also manages redirects and 404 errors, with fields for AI answers and structured data. The admin is protected with roles and 2FA, and analytics load only after consent.
Our own product
| Industry | Internal tools & platforms |
|---|---|
| Challenge | Unclear structure |
| Decision environment | Product evaluation |
| Complexity | Intermediate |
| Service | Business website |
If you need a website that you can update yourself, without a developer, this page shows what our CMS gives you in practice and why we chose to build it ourselves.
A CMS (content management system) is the place where a business changes its own website, without a developer. For us it is the base of every site we build. So whatever the CMS does well, every client site gets.
Business websites often need more than one language. A business talks to its customers in Greek, to its partners in English, and maybe to others in German or French. The same site and the same pages speak to all of them.
That is where we started. We wanted a CMS where a multilingual website is the natural way the system works.
People who run a website in several languages usually meet the same small problems. The Greek page is updated, while the English one falls behind. Photos uploaded straight from a phone make pages slow. A page changes its name, and its old address leads to an error page.
There are newer needs too. More and more visitors get answers from AI assistants and search summaries. These tools read a page differently from a person, so a site needs short, clear answers inside its content. The admin also needs real protection, because one weak password can undo every other precaution.
So the goal was to fix a whole series of small issues. Each one looks unimportant, but together they affect how trustworthy a website is.
We set some limits before we started and kept them in plain view. Tracking must respect consent, as the GDPR requires. The people who run a site are business owners, not technicians. The system must describe exactly what it does.
Limit | What it meant in practice |
|---|---|
The visitor is asked before any tracking | Analytics load only after consent, and the choice can be changed later |
Owners are not developers | Texts, images, redirects and settings change from the admin, with help text next to the fields |
Clear boundaries | The admin is available in Greek or English, and some system emails exist only in these two languages |
Fixed design | The admin has no drag-and-drop tool (page builder), and fonts are set in the design |
Because we set these limits early, they shaped the design from the start. The client knows from day one what the system includes.
The first point is agreement between the languages. Over time the versions can drift apart without anyone noticing, because each one looks right on its own. A price, an address or a legal sentence changes in one language, and a visitor in the other language reads the old one.
The second point is the weight of images. A photo at full size slows down every page that shows it, and whoever is on a phone feels it first. The third point is addresses. When a page changes its name, links from other sites still point to the old name and must lead to the new page.
The fourth point is short answers and the structured data that search and answer engines read. A page written perfectly for people needs these too, so that machines also read it correctly.
We solved each issue at its source, inside the CMS, so the site owner does not have to remember anything. The right choices happen automatically, on every page and in every language. The table shows each area and what the CMS does for it.
Area | What the CMS does |
|---|---|
Languages | Translation per text, copying from the first language, a language kept hidden until it is ready, publishing without waiting for the translation |
Images | Every upload is converted to WebP, with an AVIF version next to it when that is smaller, and fits within 1920 by 1080 pixels |
Addresses | Redirects from the admin; an automatic 301 when the slug changes; a log of 404 errors from which a redirect is created |
Answers for AI | Fields for a short answer, key points, FAQ, pros and cons |
Structured data | A policy for each type of content, which can be changed per page |
Access | Roles and permissions, 2FA, an admin address that can be changed |
Analytics | Load only after consent |
Each row is a decision that saves the site owner from a repeated task.
Four decisions stand out: languages as part of the content, automatic conversion of every image, answer fields next to the normal fields, and security as a setting. Each one saves the owner from a repeated task. We describe them below.
First, languages are part of the content model. Every text has its own language, and hreflang and the sitemap cover all public languages. Languages beyond Greek and English are added as a site setting, with no new development.
Second, the conversion is applied to every image. Whatever is uploaded is encoded again, rotated correctly using the camera data, and stripped of location information. The client uploads one clean original, and the different sizes are prepared automatically.
Third, the fields for AI answers sit next to the normal fields. The short answer and the key points are written once. They are used on the page, in its summary and in the structured data, so the visible text always agrees with the text for machines.
Fourth, security is a setting that is checked. Two-factor login works with an app or by email and can be made required. No user can give another user more permissions than their own. Analytics respect the visitor's choice before anything loads.
We expect the client's team to keep several languages in step without a developer. We also expect them to publish photos without thinking about file size, and to rename pages while visitors always find the right page. These are expected results of the design, not measured ones.
We also expect a site that answer engines understand better, because the answers are written once, in fields made for that purpose. This makes the page easier to understand. Positions in results and visits depend on many factors, so we make no promises about them.
To see how it fits into a project, read the page about business websites, the page on how we work and the article why website speed is measured on mobile. The speed guarantee shows how we check the result on delivery day.
Greek and English from the start, with a translation for every text. More languages, such as German or French, are added as a site setting, with no new development. The admin screens are available in Greek or English.
Every image is converted automatically to WebP, with an AVIF copy next to it when that is smaller, and fits within 1920 by 1080 pixels. The camera's location data is removed. You upload one clean original, and the CMS prepares the rest.
Analytics load only after the visitor gives consent in the cookie banner, and the choice can be changed later. Nothing is sent before that answer.
The CMS manages redirects from the admin and creates one automatically when the address of a page changes. It also logs 404 errors, so that each one can get a redirect. In a rebuild, the old addresses are listed one by one. Tell us about your site from the contact page.
Planner is our own tool that turns detailed specifications into an application without supervision. For every feature the test is written first, the result is checked in the browser against the design, and a quality gate decides what moves on.
A real project, shown anonymously: an information website in Greek for a paediatrician, built with Next.js and our own CMS.
Our quality and security agents are our own tool. They check every build on a fixed route: QA, UX, security, pentest, SEO/AEO, a technical audit with Lighthouse and code review.
Send a project request, or check your current website for free. We read every message ourselves.