# htmlEdit

> htmlEdit is a minimal tool for editing HTML documents visually. You point, click and type directly on the rendered page, like editing a Word document, instead of hand-editing raw HTML or re-prompting an AI. It is built for cleaning up AI-generated HTML documents (memos, briefs, one-pagers). It runs as a Mac app and a Chrome browser extension, keeps your files local and private, and is open source under the MIT licence.

## Product
- Website: https://htmledit.io
- Mac app: available on the Mac App Store
- Chrome extension: https://chromewebstore.google.com/detail/htmledit-%E2%80%94-edit-this-page/hlceldedebokicfcpnfblkppgeblhgge (makes any page editable, then copy or download the HTML)
- Source code (MIT): https://github.com/rtilleard/htmlEdit
- Privacy: https://htmledit.io/privacy (collects no user data)

## About
- Made by Robbie Tilleard (https://robbietilleard.com)

## Blog
Practical writing on editing HTML documents, using Claude and Codex together, and AI productivity.
- [The Future of Documents: Editable, Portable, AI-Native](https://htmledit.io/blog/future-of-documents): The document of the future is AI-native but human-editable, portable rather than trapped in a vendor's format, and built on the open web. HTML is quietly becoming that format.
- [Small Tools, Big Leverage: The Case for Single-Purpose Apps](https://htmledit.io/blog/small-single-purpose-tools): A tool that does one thing well beats a bloated platform that does ten things adequately. Small single-purpose apps are easier to learn, faster to use, and harder to get wrong.
- [What I Learned Building a Mac App With Claude](https://htmledit.io/blog/building-a-mac-app-with-claude): Building a Mac app with an AI coding assistant sped up the mechanical parts and let me stay in the interesting decisions, but it moved the hard work to judgement: deciding what to build and knowing when the generated code was actually right.
- [Pair-Programming With Two AIs: Lessons From Shipping htmlEdit](https://htmledit.io/blog/pair-programming-with-ai): Pair-programming with two AIs works if you stay the driver and treat them as navigators. Keep tasks scoped, review everything before it lands, and don't let either run ahead of your understanding.
- [Using One AI to Check Another's Work](https://htmledit.io/blog/cross-checking-ai): Have one AI review what the other produced, cold, without the original conversation. A fresh reviewer with no attachment to the work catches errors the author glides past. You still make the final call.
- [When to Reach for Claude, When to Reach for Codex](https://htmledit.io/blog/when-claude-when-codex): Don't pick a favourite and use it for everything. Match the assistant to the shape of the job: one for framing and judgement, the other for grinding through well-defined code. In practice you'll switch mid-task.
- [Keeping Your Data Local When You Edit AI Docs](https://htmledit.io/blog/keep-your-data-local): Editing an AI-generated document should not mean uploading it to someone else's server. Local, private tools keep your work on your machine, with no account, no upload and no tracking.
- [Claude and Codex as a Team: Divide the Work, Not the Context](https://htmledit.io/blog/claude-and-codex-team): Treat Claude and Codex like two colleagues who don't share a memory. Give each a self-contained job with clear inputs and outputs, and you get more done than trying to run one giant conversation.
- [The Two-Second Rule for Capturing Ideas](https://htmledit.io/blog/two-second-capture): If capturing an idea takes more than about two seconds, you'll lose most of your ideas. Build a capture system with almost zero friction and sort things later, not in the moment.
- [An EAST Framework for AI Productivity](https://htmledit.io/blog/east-framework-ai): Getting value from AI is a behaviour-change problem, not a tooling problem. Apply EAST (Easy, Attractive, Social, Timely) to your own workflow so the useful action becomes the default one.
- [From Draft to Done: A Workflow for AI Documents](https://htmledit.io/blog/draft-to-done-workflow): Split the work into two modes: use the model to draft and restructure, then switch to editing the rendered document directly for everything else. Knowing when to switch is the whole skill.
- [Turn a Claude Chat Into a Polished One-Pager](https://htmledit.io/blog/chat-to-one-pager): Ask the AI to produce a self-contained HTML one-pager instead of a wall of chat text, then fix the last ten percent visually rather than re-prompting.
- [Prompting for Clean, Editable HTML](https://htmledit.io/blog/prompting-for-clean-html): Ask for a single self-contained HTML file with clear structure and inline styles, and you get a document you can edit later instead of a tangle you have to re-prompt.
- [How to Review AI-Generated Content Without Losing an Afternoon](https://htmledit.io/blog/review-ai-content-fast): Don't review AI content by reading top to bottom like a proof-reader. Check the big things first (structure, claims, facts), fix errors directly in the document, and leave line-level polish for last.
- [The Human-in-the-Loop Advantage: Why Editing Beats Regenerating](https://htmledit.io/blog/human-in-the-loop): When an AI document is nearly right, editing the specific bits that are wrong is faster and more reliable than regenerating the whole thing and hoping the good parts survive.
- [Stop Re-Prompting: A Faster Loop for Fixing AI Drafts](https://htmledit.io/blog/stop-re-prompting): When an AI draft is 90 percent right, don't re-prompt to fix the last 10 percent. Edit the output directly, because re-prompting risks losing the good parts and burns your time.
- [The Last-Mile Problem: Editing AI Output Without Re-Prompting](https://htmledit.io/blog/last-mile-editing): Re-prompting to make small edits is slow and unpredictable. For final tweaks, edit the rendered document directly instead of asking the AI to regenerate it.
- [WYSIWYG vs Raw Code: Editing on the Live Page](https://htmledit.io/blog/wysiwyg-live-page): Editing the live rendered page, what you see is what you get, is faster and less error-prone than hand-editing raw HTML. For documents, it is almost always the right choice.
- [The Case for HTML as a Document Format](https://htmledit.io/blog/html-as-a-document): HTML is portable, universal, single-file and free of proprietary lock-in. For everyday documents it beats the usual word-processor and PDF defaults on almost every practical measure.
- [Why AI Tools Keep Giving You HTML (and Why That's a Gift)](https://htmledit.io/blog/why-ai-writes-html): AI tools default to HTML because it is structured, universal and easy to render. That is a gift: you get a portable, editable document instead of a screenshot or a locked format.