/taylordotcat

I’m Bringing My Personal Website Back by Talking to My Agents

agents, ai, website
The current taylor.cat homepage with Axel Taylor's portrait

My personal website, taylor.cat, had gone quiet. I didn’t have time to maintain it, let alone expand it and write articles for it.

A personal website sounds simple until you have to keep it alive. Pages become outdated. Projects need descriptions. Something needs fixing. And writing an article means finding the time to turn a rough idea into something you’re willing to put your name on.

None of those jobs has to be particularly difficult. They still need attention, and I wasn’t giving the site enough of mine.

Now I’m bringing it back with agents and Grok Bot. I can start by talking: explain a change, send a voice note, or describe an article I want to write. That gives me a way to move the website forward without having to do every part myself.

An article can start as a conversation

There’s a difference between having something to say and being ready to write it.

An idea might be clear enough to explain out loud but not clear enough to structure into an article. Opening a blank editor means dealing with both problems at once: working out the thought and finding the words.

With an agent, I can start earlier. A rough message or voice note is enough to begin shaping a draft. I don’t need a headline, an introduction, or a finished argument before asking for help.

Once there’s a draft, I have something concrete to respond to. I can point out what’s missing, reject an interpretation, add context, or explain why a sentence doesn’t sound like me. The conversation helps me work out what I actually want to say.

That still requires judgment. An agent shouldn’t fill gaps with experiences I never had or opinions I don’t hold. I need to check that the writing represents me, not just that it reads smoothly.

The website needs more than a writer

Writing is only one part of keeping a personal site current. The content also needs a home, and that home needs maintenance.

My site’s code lives on GitHub and is hosted on Cloudflare. I have Quill for writing and editing, and Weaver for website implementation. Those are different jobs: helping me explain an idea isn’t the same as changing how a page works.

The workflow I want to build around them is straightforward. I capture an idea in text or a voice note, develop it with the writing agent, and review the result. When it’s ready, the website agent can prepare the changes needed to put it on the site.

Illustration of an agent-assisted writing and website workflow

The same approach can apply beyond articles. I can describe an outdated page, explain a section I want to add, or ask for a specific improvement. A conversation becomes the starting point for a concrete piece of work.

Before anything goes live, I still want to review it. Does the page say what I intended? Do the links work? Is it readable on a phone? Did anything change that wasn’t supposed to?

Automation is useful when it reduces the work without removing my control over the result.

Making the site manageable again

I’m not trying to create a website that generates content while I ignore it. I want a personal site that reflects what I’m doing and thinking, without every update becoming another project I have to find time for.

Agents can help with drafting, editing, maintenance, and implementation. I still provide the ideas, decide what belongs on the site, and take responsibility for what appears under my name.

What changes is how much preparation it takes to begin. I can explain what I need, work through the details in conversation, and review the result instead of doing every step alone.

This article starts that way too: with a short message about a website I hadn’t had time to maintain, and how talking to my agents could help me bring it back.