The Story Behind Termerly Roaderly and Vlogerly

There's a moment in every developer's life where you find yourself, for the umpteenth time, copying and pasting the same code, creating the same pages, configuring the same services. It's like living in an infinite loop where each new project becomes a technical déjà vu. That was me, a couple of years ago, before Termerly, Roaderly, and Vlogerly were born.

The problem nobody wants to admit

Every time I started a new project, the ritual was always the same. First, manually create the legal pages: Terms and Conditions, Privacy Policy, Cookie Policy. Then, if the project warranted it, set up some feedback management system or roadmap. And finally, if I was lucky and had time, implement a blog.

But let's be honest: most of the time, I didn't even get to the roadmap or blog. Why? Because it was tremendously laborious. Because each project had a different tech stack. Because when I thought about using third-party services like WordPress, I found myself spending more time configuring and deploying than building the actual features of my application.

It was a vicious circle of inefficiency that was consuming me.

The birth of a solution

Then I asked myself a simple but powerful question: Why don't I have a service where I can manage all this in one place? A centralized hub where I can create legal pages, manage feedback, publish blog articles, all without worrying about complex configurations or repetitive deployments.

The answer was obvious: I had to create it myself.

When creating legal pages makes you lose your mind

Imagine having to create the same static pages for the legal center of each of your projects. Privacy policies identical in structure, terms and conditions with slight variations, cookie policies that basically say the same thing. It's boring. It's repetitive. It's a waste of valuable time.

Initially, I tried to solve this by creating templates. I had a folder with my "base legal pages" that I copied from project to project. But here's where the real problem arose: not all my projects used the same tech stack. One project in Nuxt, another in Next.js, one more in vanilla JavaScript. Each time I had to adapt the template, adjust the format, verify that everything looked good in the new environment.

I know it wasn't something that would take me a week of work, but added to all the other tasks, they were precious hours that I could be dedicating to building real features.

Termerly was born from that frustration. A platform where I can create, manage, and publish all the legal pages of my projects from a single place. With a rich editor based on Tiptap, I can draft professional policies in minutes. Each project has its own public "Legal Center" where visitors can access all policies without me having to worry about design, hosting, or structure.

Now I don't spend more than an hour on the entire legal setup of a new project. I just create the content and that's it. Published, synchronized, accessible.

Building the community I always wanted

Roaderly has a different story, more personal. I was always excited about the idea of having my own feedback center. Not just as an administrative tool, but as a space where users could truly participate in the product's evolution.

When I worked on a platform that handled around 3,000 monthly users, I found myself needing to implement a feedback management system. I researched the options available in the market: Canny, Frill, ProductBoard. They were all good tools, but they had problems I couldn't ignore.

First, the prices. For a growing startup, the costs were hard to justify. Second, and more importantly, most of these platforms didn't give users a real voice. They were basically glorified suggestion boxes. They didn't allow creating a real community where users could vote for the best ideas, comment on others' proposals, feel part of the development process.

I wanted transparency. I wanted users to see exactly what we were working on, what was on the roadmap, what ideas were being considered. I wanted to build trust by showing that we were really listening.

I know that when platforms reach a certain level of maturity and have an established user base, new updates depend largely on what those users want. That's where tools like Roaderly become invaluable. Not just for collecting feedback, but for building a committed community that feels part of the product.

Roaderly is that space. A public portal where users can submit ideas, vote for the ones that interest them most, follow progress in real-time through colorful and intuitive stages. And for me, as a product creator, it's a direct window into what my audience really needs.

Because writing should be simple

I always wanted to have my own blog. More than that, I always wanted each of my platforms to manage its own blog independently but efficiently.

In the past, I compensated for this need by using custom software and headless CMS like Strapi or Prismic. They worked well, but they added complexity. I had to maintain another application, manage another deployment, worry about another database.

Then I tried WordPress. Yes, I tried it, and it was an interesting experience. But I quickly realized that I was spending more time setting up a blog in WordPress than doing it myself from scratch. I had to look for themes, customize them, create my own templates to make them look the way I wanted, deal with plugins that sometimes worked and sometimes didn't.

It was absurd. Here I was, a developer perfectly capable of building modern and fast interfaces, fighting with a WordPress editor that insisted on adding inline styles that broke my design.

Vlogerly is my answer to that problem. A blogging platform built with the same modern architecture I use in my other projects: Nuxt 4, Turborepo, Drizzle ORM, PostgreSQL. A rich editor based on Tiptap that gives me all the flexibility I need without compromising the experience.

Now each project has its own "Blog Center" where I can publish articles, manage categories, add tags, all from a unified interface. And the best part: everything is automatically optimized for SEO, with dynamically generated Open Graph images and real-time updated sitemaps.

The pattern behind the solutions

If you look closely, Termerly, Roaderly, and Vlogerly share something fundamental: they all emerged from frustration, but were built on solid principles.

• Centralization: Everything in one place. No more scattered services, no more repeated configurations in each project.

• Simplicity: Intuitive interfaces that don't require weeks of onboarding. I want to create content, manage feedback, publish articles. I don't want to fight with the tool.

• Control: You decide what, when, and how to publish. You're not tied to the limitations of a WordPress theme or the restrictions of an inflexible SaaS platform.

These three platforms are built on a modern and scalable tech stack: Nuxt 4 for the frontend, Drizzle ORM for the data layer, Firebase Authentication for security, Cloudinary for asset storage. All connected through Turborepo, sharing code where it makes sense, maintaining independence where necessary.

The impact on my workflow

Since I launched these platforms, my development process changed radically. Before, a new project meant days of prior configuration. Now:

1. I create a new project in Termerly and draft the legal pages in less than an hour.

2. I set up a roadmap in Roaderly in 15 minutes, and I already have a public space where users can start submitting feedback from day one.

3. I set up a blog in Vlogerly in minutes, and I can start publishing content immediately.

What used to take me days, now takes hours. What used to be a tedious task is now almost pleasurable.

The most important lesson

These platforms not only solved my technical problems; they changed my mindset about product development. They taught me that the best solutions don't always come from looking for the perfect tool in the market, but from deeply understanding your own problem and building exactly what you need.

I'm not saying every developer should build their own tools. But I do believe that when you find yourself repeating the same painful process over and over again, it's worth asking yourself: Is there a better way? And if it doesn't exist, can I create it?

Termerly, Roaderly, and Vlogerly exist today because I asked myself those questions. And now, they're not just tools I use daily, but products I'm taking to market so that other developers and businesses can benefit from the same efficiency I've gained.

What now?

These platforms are in production, maturing, evolving. Each has its roadmap (managed in Roaderly, of course), its blog (in Vlogerly, naturally), and its legal pages (all in Termerly, as expected).

But more important than that: they're solving real problems for real people. Including me, which is where it all started.

Because at the end of the day, the best tools are those that are born from genuine needs, not market speculation. And these three platforms are living proof of that.

If you identify with these problems and want to try the solutions I created, you can explore Termerly for your legal pages, Roaderly for feedback management, or Vlogerly for your blog. All are completely free.