Implement hybrid brand assets strategy (Git + CDN)

Start by reading aRustyDev/ai/.ai/plans/repository-ecosystem-strategy.md, then review the proposed source/, dist/, .github/workflows/, and brand-guide.md entries in this issue. Done means the asset structure, Git LFS setup, optimization and CDN workflow, DNS configuration, usage guide, and consumer URL documentation are all implemented.

Overview

Implement a hybrid approach for brand assets that combines Git version control with CDN delivery for optimized production use.

Strategy

Repository Structure

arustydev/brand/
├── source/              # Original files (AI, SVG, PSD) - Git LFS for large files
│   ├── logos/
│   ├── colors/
│   └── typography/
├── dist/                # Optimized outputs (PNG, WebP, JSON)
│   ├── logos/
│   ├── favicons/
│   └── palette.json
├── brand-guide.md       # Usage guidelines
└── .github/workflows/   # Auto-optimize on push, deploy to CDN

Delivery Methods

Implementation Tasks

• Set up Git LFS for large binary files (AI, PSD, etc.)
• Create source/ directory structure for original assets
• Create dist/ directory structure for optimized outputs
• Create GitHub Actions workflow to:
  • Auto-optimize images on push (PNG → WebP, SVG optimization)
  • Generate favicon set from logo
  • Generate palette.json from color definitions
  • Deploy dist/ to CDN
• Configure brand.arusty.dev DNS
• Create brand-guide.md with usage guidelines
• Document URL patterns for consumers

Benefits

• Version controlled: All changes tracked in Git
• Offline development: Direct repo access works without internet
• Fast production delivery: CDN caching and optimized formats
• Automated optimization: No manual image processing needed

Related

This issue was created as part of the repository ecosystem strategy discussion.
See: aRustyDev/ai/.ai/plans/repository-ecosystem-strategy.md