Look, I've always wanted to be a better writer. But I have ADHD. You know what kills good ideas? The executive function tax.
You have a brilliant insight at 2 PM. By 4 PM, you're still figuring out file naming. The idea? Dead. Buried under technical friction.
So I built a system that eliminates the tax. Without losing my voice.
The Copy Without an Original
Here's the uncomfortable truth: Most "authentic" content already uses tools. Spell checkers. Grammar assistants. Editing software. Research databases.
We pretend there's some pure, unmediated form of creativity. But that's just nostalgia for something that never existed.
Think about photography. When cameras were invented, painters cried "that's not real art!" Now we have honest photographers and manipulative ones. Same tools, different intentions.
We're in the "invention of AI-assisted content" moment. Just like I take honest photographs, this blog contains honest content that I have assistance writing.
I'm using AI to write about using AI to write. It's simulacra all the way down—a copy without an original. But here's what I discovered: The more friction I remove from publishing, the more my actual voice comes through.
Here's What I Actually Built
My AI-Assisted Content Stack (Takes 5 minutes total):
- 🤖 Claude Code - Writing partner + technical co-pilot
- 🔍 Perplexity - Research + fact-checking
- ⚙️ Personal MCP Server - Custom automation tools
- 📝 Blog Post Workflow - Zero executive function tax
- 🚀 Eleventy (11ty) - Lightning-fast static site generator
Result: Scattered thoughts → published post in under 10 minutes.
What You Get
✅ Zero Executive Function Tax - No mental energy spent on file structure, frontmatter, or formatting
✅ Voice Preservation - AI condenses and structures, but ideas stay mine
✅ Rapid Iteration - From brain dump to publish in under 10 minutes
✅ Full Transparency - Every prompt saved, every AI interaction documented
✅ ADHD-Friendly - Built for time blindness, perfectionism paralysis, and idea overwhelm
How It Actually Works (4 Simple Steps)
Step 1: Brain Dump (30 seconds) 📝
Me to Claude Code:
"I want to write about my AI blogging process.
Matrix references. Show my stack.
Address authenticity concerns."Step 2: Research Mode (2 minutes) 🔍
- For info-heavy posts: I research with Perplexity first, then feed context to Claude
- For this meta post: Claude researched AI transparency trends directly
- Claude Code reads my existing blog posts for voice patterns
- Sometimes I provide my own research as context
Step 3: Auto-Structure (2 minutes) ⚙️
- ✅ Generates frontmatter (title, date, meta description)
- ✅ Applies my voice patterns from existing posts
- ✅ ADHD-friendly structure: problem → solution → benefits
- ✅ Creates file with proper naming in correct folder
Step 4: Human Edit (5 minutes) ✏️
I review everything. Mostly prompt for edits and make small changes. If the AI output is good enough and sounds like me? I ship it. No need to rewrite for the sake of rewriting.
That's it. Idea to published post in under 10 minutes.
Real-World Impact
Before (The Old Map):
- 💭 Great ideas lost to technical friction
- 📝 Posts rot in drafts folder for months
- 🧠 Executive function paralysis
- ⏰ "I'll publish when it's perfect" (never happens)
After (The Territory):
- ⚡ Brain dump to published post in 10 minutes
- 📅 Ideas captured and published same day
- 🎯 Energy focused on ideas, not file organization
- 🚀 "Good enough" shipped beats "perfect" never-published
Real numbers: I've published 8 posts in 2 weeks using this system. Before AI workflow? 2 posts in 6 months.
Full Transparency: How I Use AI
AI is my research assistant and first-draft writer:
- 🔍 Finds current info and trends (Perplexity)
- 📝 Organizes my messy thoughts into structure (Claude Code)
- ⚙️ Handles boring tech stuff (file naming, formatting)
- 🎯 Studies my old posts to match my writing style
- 📄 Creates rough drafts for me to edit
About your data and privacy:
- 📊 I track which posts people read (using PostHog analytics)
- 💡 This helps me write better content you actually want
- 🔒 I will never sell your data. Ever.
- 🎯 Analytics only help me improve the blog experience
What I personally do:
- 💭 All original ideas and insights come from me
- ✏️ I review and prompt for edits (not rewriting everything)
- 📚 I add personal stories when needed
- 🎯 I make all final decisions about tone and message
- ✅ I take full responsibility for everything published
What I never do:
- ❌ Copy-paste AI output without editing
- ❌ Mass-generate content for SEO
- ❌ Hide that I use AI tools
- ❌ Let AI decide what gets published
The Stack Deep Dive
Claude Code Integration:
// Typical workflow interaction
User: "Help me write about X topic"
Claude: *researches topic, analyzes existing content*
Claude: *structures according to blog-post-workflow.md*
Claude: *applies voice patterns from CLAUDE.md style guide*
Claude: *generates properly formatted HTML with frontmatter*Perplexity for Research:
- Current trends and statistics
- Fact-checking and verification
- Industry best practices
- Competitor analysis
Personal MCP Server Features:
- Custom blog post templates
- Automated file naming and organization
- Frontmatter generation
- Voice consistency checks
Why Eleventy (11ty) for the Blog:
- ⚡ Builds in milliseconds (not minutes like Gatsby/Next.js)
- 📄 Simple HTML files with YAML frontmatter
- 🎯 No JavaScript bloat - just clean, fast HTML
- 🔧 Works with multiple template languages (I use HTML + Liquid)
- 🚀 Perfect for ADHD: `npm run start` and it just works
The beauty? Eleventy stays out of my way. Claude writes the HTML files, it generates a static site. No framework lock-in, no complex build configs. Just AI + words → website.
Addressing the Big Concerns
"Is this really your voice?"
Yes. AI helps me structure and format, but every insight, experience, and opinion comes from me. It's like having a really good editor who never gets tired.
"What about authenticity?"
I'm being more authentic by removing the barriers that prevented me from sharing ideas. The technical friction was hiding my voice, not preserving it.
"Are you mass-generating content?"
Absolutely not. Each post starts with my specific ideas and experiences. AI helps me organize and polish, not generate from nothing.
"Why not just write normally?"
Because "normally" meant ideas dying in drafts. This system ships ideas while they're fresh and relevant.
Resources to Build Your Own
Want to create a similar workflow without my exact setup? Here are the key components:
- Claude Code - AI coding and writing assistant
- Perplexity - AI-powered research tool
- MCP Servers - Custom tool integration
- ADHD Automation Guide - Neurodivergent-friendly workflows
- Executive Function + AI - Using AI to reduce cognitive load
The Bigger Picture
This isn't just about blogging faster. It's about eliminating the friction that kills good ideas.
Every person with ADHD knows the frustration: brilliant insight at 2 PM, but by the time you've set up the document structure, it's 4 PM and the idea feels stale. Executive function tax claimed another victim.
AI doesn't replace creativity—it removes the administrative overhead that buries it.
My commitment: I will always disclose AI usage, save all prompts for transparency, and maintain editorial control over published content. Better to be honest about the process than pretend it's all manual when the real value is in the ideas, not the formatting.
Try This Approach Today
Start simple:
- Pick one AI writing tool (Claude, ChatGPT, or similar)
- Create a simple template for your content format
- Practice brain dumps - messy ideas first, structure second
- Edit everything - AI gives you a starting point, you make it yours
- Be transparent - tell readers about your process
The goal isn't perfect content. It's shipping ideas that matter.
Ready to eliminate your own executive function tax? The tools exist. The question is: what ideas are you not sharing because the process feels too hard?
Meta Layer: Live Editing This Post About AI Editing
Since transparency is the whole point, here's what happened during the creation of THIS post:
Initial Creation (10 minutes):
- ✏️ Brain dumped my requirements to Claude Code
- 🔍 Claude researched AI transparency concerns (not Perplexity this time)
- 📝 First draft generated with Matrix references and ADHD focus
Live Edits During Recording (still happening!):
- ❌ "I've been obsessed with writing for years" → ✅ "I've always wanted to be a better writer" (more honest)
- ❌ "Perplexity finds current AI transparency trends" → ✅ Clarified my actual research process
- ➕ Added Eleventy (11ty) explanation after realizing I never mentioned the actual blog framework
- 🔍 Used WebFetch to research 11ty.dev for accurate description
- ✏️ Clarified editing process: "I mostly prompt edits and do small changes" (not rewriting everything)
- 🎭 Removed Matrix red pill/blue pill theme (too politically loaded) → Baudrillard's simulacra
- ✅ "I write HTML files" → "Claude writes the HTML files" (full honesty mode activated)
- 🎥 Recording stopped but will add path to video soon
- 🤔 Title changed from Matrix theme to "The Copy Without an Original"
- ➕ Added real conversation examples to show my actual AI workflow
- 🎭 Added meta-irony section about the double negative of transparency layers
- 🤖 Added section about prompting strategy and typical editing prompts I use
- ✏️ Rewrote meta-irony section - changed from "double negatives" to "using dishonest tools honestly"
- 📝 Final proofread - changed "most people see AI" to "AI often gets used" (less presumptuous)
- 🖼️ Updated image to alexandra-nicolae-ROc8eiAnHWg-unsplash.jpg
- ✂️ Cropped image to landscape format (alexandra-nicolae-ROc8eiAnHWg-unsplash-landscape.jpg)
- 🎭 Added "Blurry Boundaries of Creation" section connecting image cropping to AI authorship questions
- 📸 Added photo credit for Alexandra Nicolae from Unsplash
- ✂️ Re-cropped image to rule of thirds composition (removed 25% from top)
- 🎯 Fine-tuned crop positioning by going down a bit more (v2)
- 📐 Final crop adjustment for perfect rule of thirds positioning (final version)
- 📄 Changed from download link to inline documentation for workflow transparency
- 🔧 Fixed HTML escaping issues in code block (markdown breaking the layout)
- 📝 Documented this real-time editing process as part of transparency commitment
The Meta-Meta Layer:
Yes, I'm using AI to edit a post about using AI to write posts, while documenting the edits in the post itself. If this feels like looking into two mirrors facing each other, that's because it is.
It's turtles all the way down, except the turtles are made of words about words. 🐢📝🐢
The Conversation Behind This Post:
This entire post emerged from me telling Claude: "I want to create a blog post about the process of how this blog uses AI to take my ideas into blog posts." What followed was a real-time collaboration where:
- I corrected inaccuracies ("I don't use Perplexity for THIS post")
- We pivoted from Matrix metaphors when I realized the political baggage
- I kept pushing for more honesty ("Claude writes the HTML files")
- The post documented its own creation as we created it
Real Examples From Our Conversation:
Initial Brain Dump:
Me: "I want to create a blog post about the process of how this blog
uses AI... We should lightly comment on the weird copy of a copy
effect of this. but keep it accessible."How Claude Interprets My Prompts:
When I give Claude messy instructions, it uses its system prompts and context to structure responses. Key parts of how Claude works with my blog:
- Voice Matching: "Write like you're talking to a friend, not giving a lecture"
- ADHD-Friendly: "Short sentences, clear steps, visual progress indicators"
- Problem-First: "Lead with the pain point, then solve it"
- Practical Focus: "Show actual code/configs, not abstract concepts"
Claude's Internal Process (What I Imagine Happens):
My Messy Input: "matrix references but accessible, show stack,
address authenticity concerns"
Claude's Processing:
1. Parse intent: transparency post about AI workflow
2. Apply voice patterns from CLAUDE.md style guide
3. Structure: problem → solution → benefits → how-to
4. Add ADHD-friendly elements: emojis, time estimates, steps
5. Include practical examples and code snippets
6. Generate proper frontmatter and HTML structureThe Prompting Strategy:
My prompts are intentionally loose and conversational. I don't give Claude rigid templates because:
- Context is everything: Claude has my entire blog workflow and style guide
- I want surprises: Over-specific prompts kill creativity
- Iteration over perfection: Better to get 80% right and edit than overthink the prompt
- Natural language works: "make this more honest" is clearer than formal instructions
Typical Editing Prompts I Use:
"This sounds too corporate, make it more like me talking to a friend"
"Add more ADHD-friendly stuff - time estimates, emojis, progress indicators"
"This section is too long, can you tighten it up?"
"Actually that's not accurate, here's what really happens..."
"Drop the jargon, my audience includes non-technical people"
"Can we make this funnier/more playful?"Correcting Inaccuracies:
Me: "Perplexity finds current AI transparency trends (this is not true
but maybe mention the fact that for most information based blog post
I do some research with perplexity..."
Claude: [Updates to clarify actual research process]Pushing for Authenticity:
Me: "Look, I've been obsessed with writing for years, thats not really
true. I feel like I have always wanted to be a better writer"
Claude: [Changes opening to be more honest]Recognizing Problems:
Me: "oh no I wish that I could do this theme but taking the AI red pill
is too right wing sounding. Can we drop the matrix theme"
Claude: [Pivots to Baudrillard's simulacra concept instead]Full Transparency Mode:
Me: "The beauty? Eleventy stays out of my way. I write HTML files...
actually straight up claude does write it too"
Claude: [Updates to "Claude writes the HTML files"]This is how I actually use AI - constant back-and-forth, corrections, pivots, and pushing for more accuracy and authenticity. It's collaborative editing, not blind acceptance.
Using "Dishonest" Tools Honestly:
Here's what I find interesting: AI often gets used for deception. Fake reviews. Corporate nonsense. Mass-produced content slop.
But I'm doing the opposite. I'm using something often associated with dishonesty for radical transparency. Full disclosure. Real conversations. Actual process documentation.
It's like using a tool designed for forgery to create the most authentic signature possible. The tool isn't inherently dishonest - it's how you use it that matters.
So yes, Claude is writing about Claude writing about Claude. But every layer is documented, every edit is tracked, every conversation is preserved. That's more transparency than most "authentic" content provides.
The Blurry Boundaries of Creation:
Even something as simple as cropping an image changes what it means. I just cropped the header image for this post from portrait to landscape - same pixels, different story. The photographer's intent? Shifted. The viewer's focus? Completely different.
Sometimes photography doesn't even involve a camera anymore. Digital art. AI-generated images. Photo manipulation that creates scenes that never existed.
AI has these same weird properties. Where does my thinking end and Claude's begin? When I prompt "make this sound more like me talking to a friend," whose voice is that? When Claude suggests a better structure and I accept it, who authored the organization?
The boundaries are fuzzy by design. And maybe that's okay. Maybe trying to draw clean lines between "human" and "AI" creation is like trying to separate the dancer from the dance.
The Complete Workflow Documentation:
Want to see exactly how this AI-assisted blogging system works? Here's the full workflow, style guide, and technical documentation that powers this process:
==============================================
AI-ASSISTED BLOGGING WORKFLOW - COMPLETE
==============================================
This document contains the complete workflow documentation from Justin Quaintance's
AI-assisted blogging system, as referenced in "The Copy Without an Original"
blog post.
See exactly how AI-assisted content creation works in practice, with full
transparency and reproducible workflows.
Source: https://github.com/justinquaintance/eleventry-blog
Blog post: https://jquaintance.com/blog/software/behind-the-matrix-ai-assisted-blogging-transparency/
==============================================
1. PROJECT OVERVIEW (README.md)
==============================================
## Justin Quaintance Blog
Personal blog built with Eleventy and Epic CSS, managed with Nix flakes.
## Development
**Prerequisites:** Nix with flakes enabled
```bash
# Enter development environment
nix develop
# Start development server
npm run start
# Build for production
npm run build-production
```
The site will be available at http://localhost:8080
## Writing Posts
**Quick workflow:** Tell Claude Code "Turn this into a blog post" and paste
your content.
**Manual process:**
1. Create .html file in appropriate category: src/blog/{category}/{slug}.html
2. Add frontmatter with title, date, description, images
3. Write content in HTML format
4. Categories: product, software, infrastructure
See blog-post-workflow.md for detailed instructions.
## Architecture
- Static Site Generator: Eleventy (11ty)
- Styling: Epic CSS with custom Sass
- Package Manager: Yarn with Nix flakes
- Dependencies: Managed via yarn.nix for reproducible builds
- Deployment: AWS Amplify Hosting (pre-built static files)
## Deployment
### AWS Amplify Setup (One-time)
1. Connect Repository:
- Go to AWS Amplify Console → "Host web app"
- Connect your GitHub repository
- Select branch: main
2. Build Settings:
- Amplify will automatically detect amplify.yml
- The configuration serves pre-built files from _site/
- No build process needed (files are pre-built via git hooks)
3. Custom Domain (Optional):
- In Amplify app → "Domain management"
- Add your domain - SSL certificates are automatic
### Deployment Workflow
```bash
# 1. Create/edit blog post
vim src/blog/product/my-new-post.html
# 2. Commit (git hook auto-builds and stages _site/)
git commit -m "Add new blog post"
# 3. Push to trigger Amplify deployment
git push origin main
# 4. AWS Amplify automatically deploys the pre-built _site/ directory
```
The git hook ensures _site/ is always up-to-date and committed, so Amplify
simply serves the pre-built files with zero build time.
==============================================
2. AI WRITING STYLE GUIDE (CLAUDE.md)
==============================================
# Claude Code Context for Eleventry Blog
## Blog Writing Style Guide
### Voice and Tone
- Conversational and authentic - Write like you're talking to a friend,
not giving a lecture
- Start with personal experience - Open with "I Love X, But..." or similar
personal hook
- Problem-first approach - Lead with the pain point, then solve it
- ADHD-friendly - Short sentences, clear steps, visual progress indicators
- Practical over theoretical - Show actual code/configs, not abstract concepts
### Key Phrases and Patterns
- "Look, I've been..." (personal experience intro)
- "Here's What I Actually Do" (practical section)
- "I got excited when I realized..." (discovery moment)
- "Why I'm obsessed with this approach:" (benefits list)
- "No [tool]? Just use..." (inclusive alternatives)
- "Takes about X minutes" (time-conscious)
### Structure Template
1. Hook: Personal pain point (1-2 paragraphs)
2. Quick Solution Overview: What you built (1 paragraph)
3. What You Get: Bullet list of benefits
4. How It Works: Actual implementation with code
5. Real-World Usage: Practical examples
6. Why This Matters: Bigger picture/philosophy
7. Call to Action: Try it today
### Technical Details
- File Format: .html files with YAML frontmatter
- Categories: product, software, infrastructure
- Required Frontmatter:
---
title: [Compelling, benefit-focused title]
date: YYYY-MM-DD
featuredImage: /assets/[image-name].jpg
image: /assets/[image-name].jpg
imageAlt: [Descriptive alt text]
description: [SEO meta description, 150-160 chars]
postImage: true
---
- Content: HTML tags (h2, p, ul, pre code)
### ADHD-Friendly Features to Include
- Time estimates ("This takes 5 minutes")
- Clear progress tracking ("Step 1 of 3")
- Visual indicators (✅, 📝, 🎉)
- "Good enough > perfect" messaging
- One-line summaries before details
### Blog Post Creation Workflow
See blog-post-workflow.md for the complete automated process to transform
raw content into published posts.
### Common Tasks
- Create new post: Follow workflow in blog-post-workflow.md
- Add images: Place in /src/assets/ and reference with /assets/[name]
- Image cropping: Use ImageMagick in nix-shell for optimal blog layouts
- Build site: npm run start for local preview
- Categories: Each has own JSON config in src/blog/[category]/
### Image Workflow with ImageMagick
When blog images need cropping or resizing for optimal display:
```bash
# Enter nix-shell with ImageMagick
nix-shell -p imagemagick
# Check original dimensions
identify image-name.jpg
# Crop to landscape (16:9 ratio) from top
magick convert image-name.jpg -crop WIDTHxHEIGHT+0+0 image-name-landscape.jpg
# Crop for rule of thirds composition (adjust Y offset as needed)
magick convert image-name.jpg -crop WIDTHxHEIGHT+0+OFFSET image-name-final.jpg
```
When to offer image cropping:
- Portrait images that need landscape orientation
- Images where key subjects aren't positioned optimally
- Wrong aspect ratios for blog headers
- Always preserve original files and create new versions
Crop positioning tips:
- For rule of thirds: position subjects at 1/3 or 2/3 points
- Start with mathematical calculations, then fine-tune visually
- Keep meaningful elements in frame
- Consider the story the crop tells vs original
### Writing Philosophy
- Publish over perfect - Better to share imperfect ideas than hoard
perfect drafts
- Solve real problems - Every post addresses actual pain points
- Include everyone - Always provide non-Nix alternatives
- Celebrate small wins - Encourage readers, reduce overwhelm
==============================================
3. DETAILED WORKFLOW (blog-post-workflow.md)
==============================================
# Blog Post Creation Workflow
Transform raw text files into properly formatted blog posts for your
Eleventy blog
## Core Problem This Solves
This workflow addresses the specific challenges that make blog publishing
overwhelming:
- Content Structure Paralysis: Raw ideas need proper frontmatter,
categories, and formatting
- Time Blindness: Posts sit in drafts forever without a clear publishing
process
- Technical Friction: Converting text to proper HTML/Markdown with correct
file structure
- SEO Overwhelm: Forgetting meta descriptions, images, and proper URLs
- Perfectionism Paralysis: Fear of imperfect posts prevents publishing
- File Organization: Figuring out where files go and what to name them
## The Solution: Controlled Automation
This workflow removes cognitive load while preserving creative control by:
1. Automating file structure (no mental energy spent on organization)
2. Generating frontmatter systematically (no missing metadata)
3. Converting content formats (no manual HTML/Markdown conversion)
4. Preparing but not publishing (maintaining control over final output)
When user asks for help publishing a blog post, follow this exact automated
workflow:
## Step 1: Locate Raw Content
Say: "I'll help you transform your raw content into a published blog post.
Let me find your content file."
Ask the user:
"Where is your raw blog post content?
- Paste the content directly here
- Provide a file path (e.g., ~/drafts/my-post.txt)
- I'll help you find it in your filesystem"
If they provide a path, read the file. If they paste content, capture it
for processing.
## Step 2: Content Analysis and Category Assignment
Analyze the content and determine:
1. Main topic/theme (for category assignment)
2. Key concepts (for tags and meta description)
3. Post length (for reading time estimation)
4. Tone and audience (for final formatting decisions)
Present category options based on your existing structure:
"Based on your content, I suggest these categories:
- product (product management, design thinking, user experience)
- software (development, coding, technical topics)
- infrastructure (systems, DevOps, architecture)
Which category fits best, or should I create a new one?"
## Step 3: Generate Post Metadata
Ask for essential details:
"I need some quick details for your post:
1. Title: [Auto-suggest based on content, let them edit]
2. Publish date: Today (2025-08-04) or different date?
3. Featured image: Do you have one, or should I suggest placeholder?
4. Meta description: [Auto-generate from first paragraph, let them edit]"
Keep it fast - if they say "use defaults", proceed with generated content.
## Step 3.5: Image Processing (If Needed)
If user provides an image that needs optimization for blog headers:
Check image orientation and composition:
```bash
nix-shell -p imagemagick --run "identify image-name.jpg"
```
Offer cropping if needed:
- Portrait images → crop to landscape
- Poor composition → suggest rule of thirds cropping
- Wrong aspect ratio → optimize for blog headers
Standard crop workflow:
```bash
# Landscape crop from top
nix-shell -p imagemagick --run "magick convert image.jpg -crop WIDTHx(HEIGHT*0.56)+0+0 image-landscape.jpg"
# Rule of thirds positioning (adjust Y offset)
nix-shell -p imagemagick --run "magick convert image.jpg -crop WIDTHxHEIGHT+0+OFFSET image-final.jpg"
```
Always save original and create new versions with descriptive filenames.
## Step 4: Content Formatting and Structure
Transform the raw content:
1. Convert to proper HTML/Markdown
2. Add proper heading hierarchy (H2, H3, etc.)
3. Format code blocks if present
4. Add paragraph breaks and spacing
5. Identify and format lists, quotes, etc.
Present a preview:
```
FORMATTED CONTENT PREVIEW
========================
Title: [Generated Title]
Category: product
Date: 2025-08-04
[First 200 characters of formatted content...]
Does this formatting look good? (y/n)
```
## Step 5: File Generation and Placement
Generate the properly structured blog post file using Eleventy's HTML
frontmatter format:
```html
---
title: [Post Title]
date: 2025-08-04
featuredImage: /assets/blog/placeholder.png
image: /assets/blog/design2seo-11ty-theme.jpg
imageAlt: [Generated alt text]
description: [Meta description]
postImage: false
---
[Formatted HTML content with proper tags: h2, p, ul, li, etc.]
```
Technical Implementation Details:
- File Format: .html files with YAML frontmatter (Eleventy processes
these automatically)
- Category Structure: Each category has its own JSON config file that
defines layout and tags
- Required Frontmatter Fields: title, date, featuredImage, image,
imageAlt, description, postImage
- Content Format: Raw HTML (no markdown processing needed)
- Image Assets: Default to /assets/blog/placeholder.png or existing
theme image
File naming convention:
- Convert title to slug (lowercase, hyphens, no special characters)
- Place in appropriate category folder: src/blog/[category]/[slug].html
- Use .html extension (Eleventy processes these as templates)
Category Configuration (automatic via JSON files):
- product.json: layout: "post.njk", tags: ["productPosts", "blog"],
author: "Justin"
- software.json: layout: "post.njk", tags: ["softwarePosts", "blog"],
author: "Justin"
- infrastructure.json: layout: "post.njk", tags: ["infrastructurePosts",
"blog"], author: "Justin"
## Step 6: Controlled File Creation
Ask: "Ready to create your blog post file? I can:
1. Create the file and show you the path (recommended)
2. Show you the content to copy/paste manually"
If automated creation:
1. Generate filename: src/blog/[category]/[title-slug].html
2. Create the file with proper frontmatter and content
3. STOP - Do not build or publish
4. Show the user: "✅ Blog post created at: src/blog/[category]/[title-slug].html"
## Step 7: Preview and Review Process
Offer to build and preview:
```
POST CREATION SUMMARY
====================
File: src/blog/[category]/[title-slug].html
Category: [category]
Word count: ~[count] words
Status: Ready for review
Next steps:
1. Run 'npm run start' to preview locally
2. Visit http://localhost:8080/blog/[category]/[title-slug]/
3. Review and edit as needed
4. Commit and deploy when ready
```
## Key Automation Rules
- Always preserve original content - save raw version for reference
- Generate SEO-friendly slugs - lowercase, hyphens, no special chars
- Follow existing file structure - match category folders and naming
- Include all required frontmatter - title, date, image, description
- Format content consistently - proper HTML structure and spacing
- 24-hour rule - If it's ready, encourage publishing within a day
## Error Handling
Content file not found:
"I can't find that file. Please:
1. Check the file path is correct
2. Paste the content directly, or
3. Let me search your filesystem for draft files"
Category doesn't exist:
"The category '[category]' doesn't exist yet. I can:
1. Create a new category folder and index file
2. Use an existing category instead
3. Show you how to set up the category structure"
Build errors:
"There's an issue with the generated content. Let me:
1. Check the frontmatter syntax
2. Validate the HTML structure
3. Test with a simpler version first"
No content provided:
"I need your blog post content. You can:
1. Paste it directly in our conversation
2. Provide a file path to read from
3. Let me help you brainstorm and write new content"
## ADHD-Friendly Features
- Reduces Executive Function Load: Automates file structure, naming,
and formatting
- Combats Perfectionism: "Good enough! Let's publish and iterate."
- Clear Progress Tracking: "1/7 steps complete - getting post metadata"
- Manages Decision Fatigue: Provides smart defaults for everything
- Visual Progress: "📝 Content ✅ → 📋 Metadata ✅ → 🎨 Formatting ✅"
- Time Boxing: "This will take about 5 minutes total"
- Celebrates Wins: "Amazing! Your post is ready to share with the world! 🎉"
- Breaks Overwhelm: One clear step at a time with obvious next actions
## Success Metrics
- Raw content becomes properly formatted blog post in < 5 minutes
- All required frontmatter and metadata included automatically
- File created in correct location with proper naming
- Content preserves original meaning while improving readability
- User feels accomplished and eager to publish more
- Publishing anxiety is replaced with excitement to share ideas
- Technical barriers are completely eliminated
Remember: The goal is publishing, not perfection. Better to have an
imperfect post live than a perfect post in perpetual draft status.
==============================================
END OF DOCUMENTATION
==============================================
This workflow has been used to create multiple published blog posts with
full transparency about the AI-assisted process.
For more examples and to see this system in action, visit:
https://jquaintance.com/blog/software/behind-the-matrix-ai-assisted-blogging-transparency/
Want to adapt this for your own blog? The key principles:
1. Loose, conversational prompts work better than rigid templates
2. AI handles structure and formatting, humans provide ideas and
editorial control
3. Document your process transparently
4. Focus on shipping ideas, not perfection
5. Automate the boring stuff, preserve the creative decisions
Contact: justin@jquaintance.com
License: MIT (adapt freely for your own use)
Photo by Alexandra Nicolae on Unsplash
Content on this blog was created using human and AI-assisted workflows described here. Original ideas and editorial decisions by Justin Quaintance.