Ed's Lab / Working archive

Small tools. Real learning.

This is where I keep the technical side of my content journey: SEO tools, GitHub projects, automation experiments, data workflows, and the things that break while I'm learning how they work.

I'm not presenting these as polished software products. The point is to build useful things, document the process, and get better at the technical work around content.

01 / Active builds

Projects I'm actively working through.

These are current learning projects. The scope can change as I understand the problem better, and some parts may stay unfinished.

01
Working project

Targetron Knowledge Catalog

Sep 2026

I adapted the reusable knowledge-catalog workflow I first worked through for Outscraper and ran a real-site pilot against Targetron. The pilot is complete, while the reusable workflow and interface work are still evolving.

Why I built it
I wanted to test whether the catalog workflow could become reusable instead of being tied to one website.
Working with
Python · GitHub · sitemap discovery · normalization
Current lesson
Reusable technical workflows need clearer boundaries, naming, and documentation than one-off projects.
Build notes →Private repository

02 / Public tools

Small tools built from repeated content problems.

These are simpler projects I can point people to directly. They are useful for showing how a repeated writing or SEO task can turn into a small web tool.

02
Public tool

Answer-Based SEO Article Planner

A small public tool that turns a search question, audience, angle, example, and CTA into a structured article-planning prompt.

Problem
Article planning can become repetitive when the same question-to-outline process is repeated manually.
Focus
HTML · CSS · JavaScript · GitHub Pages · Analytics
03
Public tool

Benefit Headline Creator

A small public copywriting tool for turning vague website headlines into clearer action-benefit headline options.

Problem
Headline revisions often repeat the same exercise: clarify what the reader can do and why it matters.
Focus
HTML · CSS · JavaScript · GitHub Pages

03 / Documentation

I want the notes to be as useful as the build.

Each project gives me something technical to practice, but it also gives me a technical-writing exercise. I use the same questions to keep the documentation honest.

  1. 01 What I tried
  2. 02 Why I tried it
  3. 03 What worked
  4. 04 What broke or confused me
  5. 05 What I learned
  6. 06 How it connects to SEO, content, APIs, or documentation
  7. 07 What I will try next

Some projects will become useful tools. Some will stay experiments. Failed attempts still belong here if they taught me something worth documenting.

Follow the work

The Lab will keep changing as I build.

GitHub holds the code. This site holds the story behind the code. My writing is where I go deeper into what I learned.