Build CartSnitch marketing site with landing page, docs, and about #1

Merged
cartsnitch-engineer[bot] merged 1 commits from feature/landing-page into main 2026-04-14 11:22:39 +00:00
cartsnitch-engineer[bot] commented 2026-04-14 11:12:57 +00:00 (Migrated from github.com)

Summary

Complete build-out of cartsnitch.github.io with all required pages and infrastructure.

What's Included

  • Landing page (index.html): Hero section with value prop, feature overview, and call-to-action
  • Help & Guides (docs/): Getting started guide, FAQ, and contact information
  • About page (about/): Company mission, values, and shopper-focused narrative
  • Legal pages (docs/): Privacy policy and terms of service
  • Responsive CSS (css/style.css): Mobile-first design optimized for grocery shopping context
  • GitHub Actions workflow: Automatic deployment to GitHub Pages on push to main
  • .gitignore: Common development files excluded

Design Approach

All content emphasizes the customer benefit (saving money) over features. Messaging is direct, warm, and written for busy parents. Design is clean, responsive, and mobile-optimized since users will reference it at the store.

Next Steps

  1. Enable GitHub Pages in repo settings (using main branch)
  2. QA review of all pages and links
  3. Merge to main and deploy

cc @cpfarhood

## Summary Complete build-out of cartsnitch.github.io with all required pages and infrastructure. ## What's Included - **Landing page** (index.html): Hero section with value prop, feature overview, and call-to-action - **Help & Guides** (docs/): Getting started guide, FAQ, and contact information - **About page** (about/): Company mission, values, and shopper-focused narrative - **Legal pages** (docs/): Privacy policy and terms of service - **Responsive CSS** (css/style.css): Mobile-first design optimized for grocery shopping context - **GitHub Actions workflow**: Automatic deployment to GitHub Pages on push to main - **.gitignore**: Common development files excluded ## Design Approach All content emphasizes the customer benefit (saving money) over features. Messaging is direct, warm, and written for busy parents. Design is clean, responsive, and mobile-optimized since users will reference it at the store. ## Next Steps 1. Enable GitHub Pages in repo settings (using main branch) 2. QA review of all pages and links 3. Merge to main and deploy --- cc @cpfarhood
Sign in to join this conversation.