How I plan, write, edit, and publish content using Google Documents, VI, and Visual Studio Code.
If you want to build a blog or online business, you need a repeatable content workflow—not just a list of tools, not just ideas, but a system.
This page breaks down exactly how I move from an idea to a finished, published webpage using three core tools. Each plays a different role in the process. Some are beginner-friendly. Others are more advanced.
The goal is not to use every tool right away. The goal is to understand how content actually gets created, refined, and published—so you can build a system that works for you.
Keep in mind that this is an advanced workflow. It doesn't involve the use of Wordpress-which is where most beginning workflows should start.
These steps stay consistent. What changes is the tool used at each stage.
Define the topic, target keyword, search intent, headings, monetization angle, internal links, and CTAs before writing a single word.
Create a rough version of the content—messy bullet points, rough paragraphs, and early structure. Focus on getting ideas out, not polish.
Clean up the writing, improve clarity, add headings, organize sections, insert internal links, and add monetization elements.
Feed the structured draft into Claude AI to generate the HTML and CSS layout. This bridges writing and publishing in one step.
Review the generated page, fix layout issues, update links, improve formatting, and organize files before it's ready to go live.
Deploy via Git or make direct server-level edits using VI. Quick live fixes happen here without downloading and re-uploading files.
Google Documents is the simplest tool in this workflow—and the best place to start if you're new to content creation. It's cloud-based, requires no setup, and gets out of your way.
I use Google Docs when I want a distraction-free writing environment and I'm still figuring out the structure. It's ideal for messy drafts, bullet points, and rough paragraphs without worrying about formatting.
I also use it for brainstorming and early-stage notes when I'm evaluating whether an idea is worth developing into a full article.
Visual Studio Code is the main bridge between writing and development in my workflow. It's more powerful than Google Docs, but still far more approachable than working directly on a server.
I use VS Code for structured drafts when I'm thinking about the final page layout, and for editing HTML and CSS after a page is generated. It's especially useful when I'm working with multiple files at once.
I often write in plain text or Markdown format inside VS Code, which keeps things clean and easy to move into the next stage of the workflow.
VI—or Vim—is a command-line text editor that runs inside the Linux terminal. It allows you to edit files directly on the server without downloading or re-uploading anything.
I reach for VI when I need to make quick, direct changes on the live server: fixing a typo on a live page, adjusting a CSS rule, updating a link, or editing server configuration files.
It's not a beginner tool. VI has a learning curve and works in modes—but once you understand it, it's the fastest way to handle server-side edits.
Each tool has a distinct role. You don't need all three to get started.
Don't overcomplicate the process early. Publishing consistently matters more than having the perfect setup.
Open a document and start writing. No setup, no learning curve. Just get your ideas out. This is where every piece of content begins.
Use WordPress or simple HTML to get your content live. Don't wait for the perfect setup—publishing your first page teaches you more than any tool.
Once you're publishing regularly, move into VS Code to get more control over your files, structure your drafts better, and edit HTML and CSS directly.
Only when you're comfortable managing your own server. VI is a power tool—useful when you need it, but not required for most bloggers starting out.
You don't need a complicated system to start. Start writing, publish consistently, and improve your workflow over time. Tools change—workflows scale.
Explore More Tools →