Context Vigilance Landing Page and ACE-It Rebrand

Summary

Created a landing page for the Context Vigilance project and completed the rebrand from the legacy "ACE-It" (Advanced Context Engineering) name to "Context Vigilance" across all URL paths, config, and content references.

Why Care

Context Vigilance is our framework for Human + AI collaboration -- a deceptively simple directory structure (context-v/) with four document types organized into two conceptual pairings. It arose from early adoption of AI code assistants and the realization that vibe coding, prompt engineering, and context engineering each fell short without a rigorous, filesystem-based methodology. The landing page articulates this philosophy publicly for the first time.

Implementation

Context Vigilance Landing Page (/projects/gallery/context-vigilance)

A dedicated landing page that explains the framework without jumping straight into the documentation-style view.
Page structure:
  1. Hero -- "Context Vigilance" with the core principle: manage context with the same rigor you manage code
  2. Origin Story -- 3-card grid: The Problem (AI frustrations), The Realization (AI needs more documentation, not less), The Unlock (a context-v/ directory with four folders)
  3. Two Pairings visual -- Side-by-side display of Planning mode (Specs ↔ Prompts) and Reflective mode (Blueprints ↔ Reminders) with distinct border colors
  4. Four Document Types -- 2x2 grid with descriptions, folder paths, cognitive states, key insights, and pairing relationships
  5. Why It Works -- 3x2 grid covering: specs being fast again, context window limits, AI memory limitations, team scaling, tooling composition, honesty about the hype cycle
  6. CTA -- "Create a context-v/ directory. Add four folders. Start writing."
Links through to the existing documentation-style page at /projects/gallery/context-vigilance/index for the full playbook.

ACE-It → Context Vigilance Rebrand

Renamed the project from its legacy "ACE-It" (Advanced Context Engineering) branding:
  • project-gallery.json: key ace-it → context-vigilance, all href paths updated, contentPath values updated to Context-Vigilance/ directory
  • [...slug].astro and CanvasModalButtonsContainer.astro: canvas import paths updated
  • Client projects index: reference updated
  • Content directory: renamed from projects/ACE-It/ to projects/Context-Vigilance/ (committed in content repo)
The canvas file retains its original filename (ACE-It-Canvas.canvas) within the renamed directory.

Header Navigation

Added href: "/projects/gallery/context-vigilance" so the header project popover links to the new landing page instead of jumping directly into the documentation view.

Files Changed

text 
Created:
  src/pages/projects/gallery/context-vigilance.astro

Modified:
  src/config/project-gallery.json (rebrand + landing page href)
  src/pages/projects/gallery/[...slug].astro (canvas import path)
  src/components/projects/project-section-layouts/CanvasModalButtonsContainer.astro (canvas import path)
  src/pages/client/[client]/projects/index.astro (reference update)
  package.json (version bump to 0.0.3.0)

Build Verification

  • Production build completes successfully
  • Landing page renders at /projects/gallery/context-vigilance
  • Documentation view still accessible at /projects/gallery/context-vigilance/index
  • Header navigation links correctly