Tools¶
Interactive HTML tools that live alongside the documentation. These are working tools, not screenshots — they hold state in localStorage and are usable from inside the wiki.
Status¶
| Tool | Status | Notes |
|---|---|---|
| Weekly dashboard | External (Phase 1.5) | Canonical at jesskovach/kcg-weekly-dashboard. Phase 1.5 deploys it to dashboard.kovachconsultants.com behind Cloudflare Access; the wiki cross-links rather than embedding. The older HTML in the tools archive is superseded and not migrated. |
| Content calendar 2026 | TODO (Phase 3) | From KCG-tools-archive/content_calendar_2026.html. Wrapper page in operations/communications/. |
| Repurposing map | TODO (Phase 3) | From KCG-tools-archive/kcg_repurposing_map.html. Wrapper in operations/communications/. |
| Speaker tracker | TODO (Phase 3) | From KCG-tools-archive/speaker_track.html. Wrapper in operations/stakeholder/. |
| Book progress | TODO (Phase 3) | From KCG-tools-archive/book_progress.html. Wrapper in operations/scope/. |
| UN wave map | TODO (Phase 3) | From KCG-tools-archive/un_wave_map.html. Wrapper in operations/stakeholder/. |
How tools coexist with documentation¶
A tool is interactive (drag/drop, inline editing, persistent state). A documentation page is text-heavy and renders as markdown. The Phase-3 migration rule:
- Text-heavy and low-interactivity → extract to markdown under the relevant
operations/<area>/folder. - Interactive → keep the original HTML here under
tools/, and add a thin wrapper markdown page under the relevantoperations/<area>/folder that introduces the tool and links to it.
The weekly dashboard is a special case: large enough and operationally-critical enough that it's deployed independently rather than bundled into the wiki build.