Publishing
A block-based article editor (paragraph, subheading, image, photo gallery, video, pull quote, info box), a category and tag system, an issue archive, cover story management, author and interviewee profiles, reading time, related articles.
The Longevity Show MagazineWeb App
We brought the reader-facing side and the entire editorial operation into a single application: the news site, the print issue production flow, advertising management and a KVKK-compliant membership and newsletter infrastructure.
In brief
The Longevity Show Magazine was conceived as a magazine printed quarterly and published digitally all year round. What the publisher needed was not simply “a website”: the same content had to go both to print and to the web, be published in two languages, have advertising sales tracked against it, and all of it had to be managed by a team with nine different job descriptions.
An off-the-shelf setup would have covered half of that. Print issue planning, page-level advertising reservations and obligations specific to Turkish legislation (KVKK, the Message Management System, laws 5651 and 5187) had to come from the system's own architecture rather than from plugin patches. So we wrote the platform from scratch.
What it can do
Two languages
Turkish and English are separate not only at text level but at address level: /kategori/saglik has its counterpart at /en/category/health. Every piece of content has its own translation, its own address and its own SEO fields. Untranslated content never appears on the English side — readers are not shown a half-finished translation.
AI-assisted translation
Turkish content is translated into English from the panel with one click. The translation is not saved directly but written into the form: the editor sees the result, corrects it and approves it, so responsibility for publication stays with a person. Body blocks are not sent to the model as they are — only the translatable text is extracted and put back, so block order, image paths and video addresses cannot be broken.
Print magazine production
Page plan, production board, page-level content and advertising layout, a 9:16 cover cropping tool, masthead management. The print workflow lives in the same database as web publishing; the same content can be followed in both media.
Advertising management
Advertiser records, reservations by page and format, banner management, price lists by type, payment type and method tracking. Advertising enquiries coming from the site are collected in a separate list and marked as called.
Membership and community
Reader accounts, a moderated comment system, likes. Comments are reviewed before they are published.
Newsletter and regulatory compliance
Double opt-in subscription, two-step unsubscribe, a nightly task that clears records whose retention period has expired, a cookie consent bar and consent gate, bulk consent reporting to the Message Management System. Terms of Service, Privacy and Cookie policies in two languages, editable from the panel.
Team and permissions
Nine roles (Administrator, Editor-in-Chief, Editor, Author, Graphic Design, Advertising, Finance, Technical, Reader) and a permission matrix that goes down to four operations per area. When a new panel section is added it appears in the matrix by itself. Authors see only their own articles.
File manager
An image library, a scan showing where each image is used, protection that prevents a file in use from being deleted, and a preview-enabled picker that opens in every upload field.
Search and sharing
Sitemaps, a Google News sitemap, RSS, hreflang tags, schema.org markup, page-level SEO fields, Open Graph images.
Interface
Light and dark themes, a mobile-first layout, and a focal point setting for cover images — so the subject stays in frame whether the same photograph runs wide on desktop or cropped to 9:16 on a phone.
How we worked
The whole platform is protected by automated tests. The tests don't just ask “does it work”; each one states which mistake it prevents. An image in use being deletable, an English page opening while its translation is half-finished, an unauthorised role seeing advertising enquiries — each of these was closed off with a test, and we verified that the tests really catch them by deliberately breaking the code.
Deployment runs with a single command: the version on the server is backed up before the code is sent, the database is backed up immediately before the migration, and it can be rolled back if something goes wrong.
Screens
Project details
Category
Web App
Year
2026
Build time
4 weeks
Status
Preparing for launch · the magazine publishes on 1 October 2026
Server side
PHP 8.3, Laravel 13
Admin panel
Filament 5, Livewire 3
Front end
Tailwind CSS 4, Alpine.js, Vite 8
Database
MySQL / MariaDB
AI
Claude API (translation)
Infrastructure
Ubuntu VDS, nginx, Let's Encrypt, deployment over rsync, automatic database backups
43 database migrations24 models17 panel sections591 automated tests1,737 assertions
What the client said
I wanted to run a bilingual magazine — printed quarterly, published digitally all year — from one place. I'm glad to have a team that worked out what we wanted more clearly than we did. Editorial, the print issue plan and advertising sales all met in the same system; each of the nine people sees only their own work and nobody treads on anyone's toes. We took delivery in four weeks. I'm not praising them because they're my own team — the real difference shows afterwards: when we ask for something, we get a date rather than “let's see”. I say that with the experience of years in the media industry; it matters a great deal.
Tell us what you have in mind and we'll work out whether it can be built.
What will be built, how long it takes and what it costs — we give you all three in writing.