A CMS for the work behind the page
Rolagzza brings tech articles, travel stories, news and project showcases into a personal publication. Wagtail handles the editorial records; Next.js renders the public site. This separation lets the writing workflow and the reading experience have different interfaces. An editor needs revisions, images and translation controls. A visitor needs readable pages, a useful project list and a clear path to related material. The architecture gives both sides a home without turning the reading surface into an administration tool.
English and Romanian need real URLs
The public routes explicitly use /en and /ro. That matters for a static export: each language has a page that can be linked, indexed and shared. Translations share a topic while remaining separate Wagtail pages. The source and translation can therefore be reviewed together. AI-assisted translation is a drafting tool within that workflow, rather than evidence that the two versions automatically say the same thing. Names, product stages and internal links need editorial checks in both languages.
Publication includes the build
Next.js exports static pages and Pagefind builds the search index. The repository also generates article sharing cards and RSS material. Publishing in the CMS is therefore only one part of releasing content: the frontend must be rebuilt with the actual API data. A healthy CMS cannot prove that a newly published article is visible in the static output. I verify the public URL after the build, including its canonical address and language links. The distinction prevents a successful import from being mistaken for a public release.
Where it stands
Rolagzza runs with Django, Wagtail, Redis and Celery on Hetzner, alongside a static frontend. This editorial release expands the portfolio and adds source-linked news. The next useful maintenance task is keeping the project stage and public links current as products evolve. A bilingual site becomes trustworthy through those small factual updates. More pages are valuable when they offer something specific: a product problem, an engineering decision or an honest account of what still needs validation.
Continue reading
The current portfolio, server-side AI architecture and my development workflow. Browse all projects or follow the newsletter.