All projects
Live · continuously maintainedAuthor · systems and information architecture

Living Playbooks.

A living education system that turns field experience into searchable paths, diagrams, templates, and decision tools.

Open the live playbook View source

The challenge

Solutions work spans discovery, architecture, delivery, recovery, migration, security, and executive communication. Useful knowledge was scattered across notes and repositories, so the project needed a navigation model that works both during an urgent engagement and during deliberate study.

The system

  • Organize field material into distinct Solutions Engineer and Solutions Architect tracks.
  • Offer alternate entry points by situation, learning path, artifact, diagram, and reusable template.
  • Publish plain Markdown through a searchable VitePress site with downloadable source material.
  • Connect the flagship to AI Engineering, Implementation, and DevOps studios as deeper branches of the same education system.

Important decisions

  • Keep Markdown as the durable source so the material remains portable and easy to maintain.
  • Treat navigation as part of the content: urgent recovery and structured learning require different paths.
  • Run link checking and the full documentation build in CI so a broken cross-reference cannot merge unnoticed.

How the work moves

  1. Step 1

    Choose an SE or SA track

  2. Step 2

    Enter by situation or learning path

  3. Step 3

    Move from guide to diagram

  4. Step 4

    Copy a reusable template

  5. Step 5

    Follow a connected studio deeper

Current evidence

  • Solutions Playbook is live on GitHub Pages with 111 resources and 13 diagrams.
  • Its content spans pre-sales, implementation, architecture, migrations, compliance, recovery, and stakeholder management.
  • The connected AI Engineering, Implementation, and DevOps sites are also published as live learning environments.

What it taught me

  • Information architecture determines whether deep knowledge is useful under pressure.
  • A living system needs build checks and maintenance standards, not just more content.
  • Teaching material becomes stronger when architecture, customer context, and delivery mechanics stay connected.

Continue exploring

Return to selected work