Skip to content

Evolve Knowledge Base — VA Guide

Welcome. This site is the single source of truth for how Evolve does things — gotchas, procedures, client-specific patterns. Use it before asking Jim a question that's likely been answered before.

How to Read

Browse: Use the left nav to drill into a category (WordPress, GHL, SEO, etc.).

Search: Press / or click the search icon to search across every lesson. Search is fast and matches lesson titles + bodies.

Categories to know: - Lessons → WordPress / Hosting & Infra / SEO / Platforms — gotchas and rules ("X breaks when Y; do Z instead") - SOPs — step-by-step procedures ("How to do X from start to finish") - Client-specific — patterns scoped to one client (Ianniello Anderson, Joe Templin, etc.)

How to Contribute a Lesson

You'll discover gotchas as you work. When you do, tell Claude in your session and ask Claude to log it. Don't fill out anything else — Claude handles the submission.

A typical exchange:

You: "Hey, that JetEngine listing took an extra step that's not in the lesson — log this so we don't trip on it again."

Claude: "Got it. I'll queue this for Jim's review."

Claude appends a row to the response sheet that Jim batch-reviews each week. Approved lessons appear on this site within 10 minutes of his commit.

What Claude needs from you

  • What happened (the surprise, the workaround, the rule)
  • Why it matters (when did this come up, what would have gone wrong)
  • Where it applies (a specific client? all WordPress? all GHL?)

Claude figures out the right category and writes the entry. If Claude's not sure how to phrase it, it'll ask before queueing.

Don't submit

  • Routine task completions (those go in your daily log, not here)
  • Questions ("How do I X?") — ask Jim directly
  • Strategy / opinion content
  • Anything containing client passwords or credentials (sensitive data stays in Bitwarden)

Format Cheat Sheet

A good lesson body fits this shape:

Rule: One-sentence statement of what to do or not do.

Why: The reason. Often a past incident or strong preference. "Last month, X happened because Y" or "Jim wants Z because [strategic reason]."

How to apply: When/where this rule kicks in. "Whenever we [do X]" or "If you see [condition], do [action]."

Knowing the why lets the next person judge edge cases instead of blindly following.

Questions?

Ask Jim. The knowledge base is a contribution to future-you and your teammates — if something's unclear, it's probably worth a lesson.