About

Discover the story behind VerdinCore, meet its creator, and explore the experience, ideas, and real-world work that shaped the platform.

There's a person behind the code

Every software product is the result of thousands of decisions. Some are technical. Others concern how people work, what deserves their attention, and which problems are worth solving in the first place.

VerdinCore is no exception.

What eventually became VerdinCore began in 2017 as a practical response to real publishing needs. It was developed, tested, and continuously refined on live websites, where ideas had to prove themselves through everyday use rather than impressive demonstrations.

For years, that work happened quietly. The platform evolved, websites were built and maintained, features were added or deliberately left out, and lessons from actual use found their way back into the software.

There was no public product story to tell. The work itself was the priority.

Today, VerdinCore has a name, a public presence, and a body of documentation that makes its capabilities and design decisions accessible to others. Something that was once known to only a handful of people is finally out in the open.

But software does not build itself.

The human side of the platform

My name is Tom Papatolis. I'm a software engineer, and VerdinCore is the result of years spent building, operating, questioning, and improving software.

I believe the experience behind a product matters. Not because experience makes every decision correct, but because working with the consequences of those decisions teaches you things that specifications and demonstrations cannot.

The Behind VerdinCore page tells more of that story: my background, the motivation behind the platform, and the perspective that continues to shape its development.

The conversation starts here

Making VerdinCore public is more than publishing documentation. It is an invitation to discover the platform, question its decisions, and consider what it might make possible.

Perhaps you're exploring a CMS for a project. Perhaps you see an opportunity to collaborate. Or perhaps something here has simply caught your attention.

Whatever brings you here, the Contact page is an open door to a conversation.

After years of building something largely out of public view, I'm interested to see where that conversation leads.