chore: update documentation and remove obsolete site files

- Updated the .gitignore to include the 'site/' directory to prevent tracking of generated files.
- Renamed "Variable Contract" to "Variables Contract" for consistency across documentation.
- Removed multiple obsolete HTML files and assets from the site directory to streamline the project structure and improve maintainability.

Author: marklearst

.gitignore

@@ -1,3 +1,4 @@
 node_modules
 .vercel
 .env*.local
+site/

README.md

@@ -139,7 +139,7 @@ See [Implementation Checklist](docs/adoption/implementation-checklist) for compl
 
 ### Contract reference
 
-- [Variable Contract](docs/contract/variable-contract) - JSON shape and structure
+- [Variables Contract](docs/contract/variable-contract) - JSON shape and structure
 - [Groups](docs/contract/groups) - Group structure and extension
 - [References](docs/contract/references) - Reference syntax and resolution
 - [Modes](docs/contract/modes) - Mode structure and resolution

docs/faq.md

@@ -25,6 +25,7 @@ Not immediately. Variable Contract provides migration paths from existing format
 ## What tools do I need?
 
 Any DTCG-compliant tool works. Variable Contract is tool-agnostic. Common tools:
+
 - Figma (authoring)
 - Style Dictionary (output generation)
 - DTCG validators (validation)
@@ -63,6 +64,7 @@ Use an adapter to normalize tool-specific syntax to Variable Contract format. Se
 ## How do I validate variables?
 
 Run validation in CI:
+
 1. Validate JSON structure
 2. Validate naming convention
 3. Validate reference resolution
@@ -111,6 +113,7 @@ See [Conformance](reference/conformance) for conformance requirements and report
 ## What if I find a bug?
 
 Report issues via GitHub issues. Include:
+
 - Variable Contract version
 - Steps to reproduce
 - Expected behavior
@@ -119,4 +122,3 @@ Report issues via GitHub issues. Include:
 ## Can I use Variable Contract with my design system?
 
 Yes. Variable Contract is design-system agnostic. It governs variable structure and governance, not design decisions (values, colors, spacing).
-

docs/index.md

@@ -9,8 +9,8 @@ Public spec for design variables: JSON shape, naming, references, modes, and cha
 ## Start here
 
 - [Why Variables](introduction/why-variables) - Why we call them variables, not design tokens
-- [Variable Contract](contract/variable-contract) - JSON shape and structure
-- [Variable Governance](governance/overview) - Governance principles and workflow
+- [Variables Contract](contract/variable-contract) - JSON shape and structure
+- [Variables Governance](governance/overview) - Governance principles and workflow
 - [DTCG Alignment](contract/dtcg-alignment) - DTCG 2025.10 compliance
 - [Getting Started](adoption/getting-started) - Team adoption guide