Üzenet Neked: A Motivational Message Website Powered by TetraCMS

When I was looking for a solution for the Üzenet Neked concept, one thing was certain: this couldn't be yet another template-based WordPress website, overloaded with plugins that nobody would dare to update six months later, just like the first version was built. The core idea is simple - a digital envelope that visitors can open to find a short, positive message inside, which they can also share with others - but turning this into a live, fast, and scalable website required a complete engine behind it. That is how Üzenet Neked became another real-world deployment of my own CMS, TetraCMS.

What Is Üzenet Neked?

At the heart of the site is the envelope animation on the homepage: with a single click, an animated envelope opens and reveals a random message from the collection. In addition, there are five themed pages, all using the same section template.

Visitors can react to every message (like/dislike) and generate a shareable image. With a single click, they get an instantly downloadable or shareable image generated from the message, sized either for an Instagram Story or a landscape post, complete with the site's own logo.

Behind the content is TetraCMS's dynamic collection model: every page, every section, and every message comes from the CMS. There isn't a single hardcoded piece of text in the templates. The website is bilingual and search-engine friendly (server-side rendering, sitemap, hreflang), and every interaction (click, view, reaction) is measured using an anonymized, hashed visitor identifier without storing raw IP addresses.

The Architecture - How It Is Built

The project is divided into three layers here as well:

An independent, static HTML/CSS/JS prototype, where the envelope animation, cards, and visual language of the shareable images are developed before anything is connected to a database.

The production public website, built with PHP 8.3+, which transforms the same design language into a data-driven experience - the envelope content, categories, and card text all come from the CMS.

The TetraCMS admin interface (Next.js) and the server-side engine, which provide a shared backbone for every Tetra-based site.

This separation means that fine-tuning the envelope animation or a shareable-image layout never blocks backend development, and vice versa - the static prototype can always be compared with the production render.

The Stack

Frontend (admin + engine): Next.js App Router, React, TypeScript, strict typing, Server Components, and Server Actions where they make sense.

Public website: Hand-written, modular PHP 8.3+ - a custom router, a custom PSR-4 autoloader, and zero external dependencies (no Composer). A motivational message website doesn't need any unnecessary framework overhead on the server.

Database: MySQL, with FULLTEXT indexing, generated-column-supported search, and hourly time-series statistics tables for views, clicks, and events.

UI layer: Bootstrap + self-hosted GSAP for the envelope animation, and GLightbox for galleries - all self-hosted, with zero CDN dependency and no third party that could slow down or track visitors.

Security: Every database query uses prepared statements, every public endpoint is rate-limited, and click and reaction targets are transmitted between the browser and server as encrypted tokens - raw identifiers never appear in the DOM.

Why Was It Worth Building as an Engine?

TetraCMS is more than just the Üzenet Neked admin interface - it is a cross-project knowledge base that every new site continues to refine. Lazy loading behind the envelope animation, the shareable-image generator, and full-text search are all patterns that are now available to any future Tetra-based site as one-time development investments.

The result is a fast, bilingual, measurable website that a single person can maintain through the CMS - while the engine behind it follows exactly the standards I would expect from a modern React/Next.js + PHP/MySQL stack in 2026: strict typing, prepared statements everywhere, zero third-party CDN dependency, and measurable performance behind every decision.

Következő projekt

OneTap