Skip to main content

Pacing Tech Stack Docs

This is the internal operating manual for the Pacing stack: tools, architecture, scripts, prompts, guides, and active project playbooks.

Use this docs site to find how systems work, where source files live, and how to make safe updates.

Start Here​

  • Architecture - live system map, key IDs, tracking flow, and integration overview.
  • Tools overview - every platform in the stack with ownership, costs, access, and dependencies.
  • Workspace Scripts - operational scripts, exports, and downloadable script packs.
  • Guides & Playbooks - step-by-step implementation guides for tracking, migration, and setup.
  • Prompts - reusable AI prompt library for infra, dev, marketing, and client work.
  • Projects - deeper implementation docs for active internal systems.
  • Docusaurus Overview - how this docs platform is structured and maintained.

Core Functions of This Documentation​

  • Single source of truth - one place for architecture, tooling, and operational process.
  • Operational readiness - scripts, runbooks, and guides linked to the real systems they support.
  • Change safety - clear separation between editable source docs and generated docs.
  • Knowledge transfer - makes onboarding faster for team members, freelancers, and future maintainers.

Edit Workflow (Important)​

  1. Pull latest changes: git pull origin main
  2. Edit source files (not generated files):
    • tools/*.md for tool documentation
    • scripts/resources/<tool>/README.md and related files for script docs
    • docusaurus/docs/*.md for custom pages and guides
  3. Commit and push
  4. Let Docusaurus render and publish

Source of Truth in Repo​

  • README.md - high-level repo orientation
  • architecture.md - canonical architecture and tracking reference
  • tools/ - primary source for tool documentation
  • scripts/resources/ - scripts, exports, backups, and runbooks

If a page in docusaurus/docs/tools/ conflicts with tools/*.md, trust tools/*.md and re-sync via build.