Contents

ai-tarkvara

How Claude Became Our Webmaster

Jarmo Tuisk3 min read
How Claude Became Our Webmaster

During the holidays we gave the Productory website a complete overhaul and now Claude Code manages and develops our entire site.

Five Years with Webflow

For about 5 years, our website ran on Webflow. I started experimenting with Webflow years before Productory was even born - several client websites and product prototypes were built with it. Webflow offered an unmatched convenience for creating and managing websites.

But by last autumn, it became clear that traditional CMS and "manual" development were falling behind the times. AI agents could do everything faster and better.

Searching for a Solution

And so the search for a solution began. First, I tried to create a system where Claude Code would connect to Webflow via API. But that only solved the content management question, and even that was clunky. I soon abandoned that approach.

I started exploring options and CMSs that would work with markdown files, since Claude would be great at writing those. I found the Astro framework and started building on it. However, it became quite clear that this wasn't suited for the AI era either. Claude feels significantly more at home coding directly rather than working through middlemen.

Claude Wrote Its Own Framework

So the final solution was that Claude wrote a complete solution from scratch that works for both of us. Technically, we use the Next.js framework with React 19 and Tailwind CSS. This combination allows Claude to write code quickly and comfortably, while I can focus on content and strategy.

In other words, the design and website you see at productory.eu is entirely Claude's work.

How Does the Work Flow?

Here's how we work - using the Ritemark editor, Claude and I create content articles by simply generating new markdown files (like blog posts). When something needs to change on another page, I just tell Claude: "Hey, add our EBS training descriptions to the homepage" or similar, and Claude writes and codes something up.

I review it, and when I say the magic words "commit and push", Claude sends the updates to the server and a few minutes later the new stuff is live. In both Estonian and English.

What About Images?

True - Claude doesn't create images itself. For that we have other AIs or a regular camera. Once the images are ready, I copy them to the files and tell Claude to add them too.

In Conclusion

Sounds like a walk in the park, right? And honestly, most of the time it is. Sometimes I still need to correct Claude's mistakes (for example, it occasionally ignores agreed-upon design rules). But that doesn't outweigh the convenience of having a machine you can simply command - go update our website!

If you want to learn how you too could use AI agents in your work, get in touch.

claudeweb-developmentai-agentsproductorynext-js