I Hated Content Editing Until I Fixed the Obvious Thing
200 lines of code and content copy writing stopped feeling like a chore
I get so energized coaxing a fresh idea into reality using ai coding agents like Claude Code. Seeing the first few iterations of your build form is an incredible dopa hit. However, the most deflating part of the experience for me has always been focusing on polishing and content editing. My excitement would go off a cliff when it was time to fine tune the written content.
Here's the paradox: I love to write! But the friction for me wasn't the writing itself. I'd get stuck in a loop where I'd look at a page in the browser, and see a change I wanted to make. Then I'd switch to a code editor, or prompt back and forth with my coding agent to find the right line, make the right change, save, flip back to the browser, check if it worked. Repeat forty times per page. It felt like trying to play chess with a pool cue, where one touch could risk scattering the pieces off the board when all I wanted was to precisely adjust one piece.
Editing content through word docs and markup files was also a chore, but for a different reason. I had more control, but I felt so disconnected from the build, and it would sap any joy out of the process.
It's not hard. It's just annoying, and I can make a hundred excuses not to do an annoying thing.
The fix was embarrassingly simple
I built a little edit mode with about 200 lines of code, bolted onto my existing dev server. Here's what it does:
- A small toggle button appears in the corner of any page I'm developing in my browser preview
- I click it, and every editable text element gets a subtle dashed outline
- I click any text and just... type. Right there on the rendered page.
- When I'm done, I hit Save. Changes write directly back to the source files on disk.
That's it. No CMS. No database. No content management system with seventeen abstraction layers. Just: see a word, click a word, change the word, save.
Why this matters more than it sounds
The experience shift is dramatic. I think of myself as a subject matter expert and writer first, and vibe coder after. Now I feel like I'm editing content rather than coding it. I get to play to my strengths.
Context changes everything about content decisions. When I can see a headline next to the image below it, I write differently. When I can feel the rhythm of a page by scrolling through it while editing, I catch things I never would staring at markup.
The technical bit (for the curious)
It's a Vite plugin — meaning it only runs during development, never in production. Three files:
- A server plugin that accepts POST requests and writes changes back to HTML or JSON source files
- A client script that handles the toggle, contenteditable, dirty tracking, and save
- A CSS file for the UI (toggle button, outlines, status toasts)
I mark elements with a data-edit attribute. The plugin uses regex to find and replace the content in source. Changes are git-tracked like any other edit. No magic.
The structured data version is slicker — I can edit JSON records (like timeline milestones or event lists) through a panel that appears on click. But for content/copy work, the inline editing is the thing that changed everything.
The tap opened
I'm publishing more now. Not because I have more to say (I've always had more to say), but because the last mile stopped feeling like work. The distance between "I want to change this" and "it's changed" collapsed from a tedious, grinding hour to a few minutes.
If you're building anything where content quality matters (which is everything), consider: where are you seeing the output, and where are you changing it? If those are two different places, this small change can make the process so much simpler and more enjoyable.