ATAILA Newsroom · New reference · Budapest · 2026-08-18

The reader decides what gets written next

There is a new live product on our reference list, and it is a different kind from the others: nextpost.blog is not a content site but a full application — a public queue readers vote on to decide which article gets written next, with a database, sign-in and an admin portal behind it.

The idea came from a children's book

I have been blogging for years, and the same question followed me the whole way: how do I know that the thing I want to write about is the thing anyone wants to read? Traffic only ever answers afterwards. You spend two weeks on an article, publish it, and the numbers tell you it was the wrong one.

The answer did not come from a marketing article. It came from a choose-your-own-adventure book I was reading aloud to my children over a national holiday. In a book like that, a passage ends and you have to decide where the story goes — and your decision determines which block of text comes next. My children argued about it, then chose, and from that point it was their book.

Somewhere in the reading the obvious question arrived: why can't a blog work like this? Why am I guessing, when I could simply ask?

Building started on 18 August. It was live on 23 August — five days, not weeks. Not because it is simple, but because it did not start from zero: the landing zone, the environments, the database, the sign-in and the delivery path already existed. Only what is unique to this product had to be written.

How it works

nextpost.blog is a standing, public queue. Every item on it is already done — the hardware ran, the measurement happened, the failure happened; what is missing is the writing. A reader signs in with LinkedIn and votes for what they want to read, and the votes rewrite the running order. The front page shows eight weeks ahead: what is coming, when, and on which blog.

The sign-in exists for exactly one reason: a vote only means something if it comes from a real person. It is not there to build a mailing list.

Not a project — a boxed product

The public page is only half of it. Behind it sits an admin portal: the live ranking of votes, approval for the most-requested articles, and a calendar where approved topics are dragged onto the coming weeks. Whatever gets scheduled there appears on the public page immediately — no separate announcement.

This is not a one-off for a single blog. The same product can be handed to anyone who publishes regularly and would rather stop guessing.

Live, on my own blogs

nextpost currently drives two blogs at once: cloudmigration.blog — the older one, about hypervisors and leaving the hyperscalers — and privateai.blog, the new one, about private AI and the hardware under it. One queue, two blogs: every topic states which one it will be published on.

That is the part that matters as a reference. We did not build a demo — we built the tool I work with, and handed my own publishing over to it.

Why this reference is different

Our existing references — OpenMath, OpenChef, OpenChem — are content sites. nextpost is a full application: its own database, OIDC sign-in, role handling, an admin interface, scheduling, an audit trail. Same platform, same hardware, same dev/test/production path — just a bigger piece of work.

If the open question was "you can do nice websites, but can you do a business application?", this is the answer, and you can open it right now.

Look at it, then bring your own

Open the queue, sign in with LinkedIn, and vote for what you would read. And if you publish regularly and know the "what do I write next?" question well — that is precisely the thing we can hand over.