hanzo.yml declares the site: each push to main builds dist/ and
publishes it as project `computer`, which serves computer.hanzo.ai.
.hanzo/workflows/cicd.yml imports hanzoai/ci and is the only workflow.
Removed with it: the GitHub Pages and image workflows, the Dockerfile,
and docs/, a committed Pages build. The FAQ and Solutions copy name
HIPAA without a certification claim, which the certclaims gate refuses.
Co-authored-by: Hanzo Dev <[email protected]>
Adds .hanzo/workflows/cicd.yml calling the canonical pipeline and drops the
GitHub-hosted workflows it replaces. Lands here because this is where the repo
is written — git.hanzo.ai is upstream and github.com is its push mirror, so the
same change made on github.com never reaches the runner fleet.
- Replace Supabase auth with hanzo.id OAuth 2.0 PKCE flow (src/lib/auth.ts)
- Replace Supabase database queries with Commerce API client (src/lib/commerce.ts)
- Add OAuth callback page (src/pages/AuthCallback.tsx)
- Update all 19 files importing from supabase to use auth/commerce modules
- Remove @supabase/supabase-js dependency from package.json
- Delete src/lib/supabase.ts (422 lines)
- Update .env.example with IAM and Commerce API vars
- Build verified: zero Supabase imports remain
- Remove opacity-60 from Hanzo and NVIDIA logos in Partners
- Add 'Limit: One Per Customer' to DGX Spark features
- Update DGX Spark description to mention customer limit
- Update PartnerLogos to use new Techstars green and DigitalOcean logos
- Remove INCEPTION PROGRAM text from hero
- Remove repeating background image causing visual disturbances
Replace all Hanzo branding with Zoo branding across zoo.computer site:
- Update page title and meta tags to "Zoo Computer"
- Change header/footer logos from "Hanzo" to "Zoo"
- Update footer ecosystem links to point to other Zoo apps (localhost ports)
- Change copyright to "Zoo Labs Foundation"
- Update social media links to @zoo, zoo-labs
- Fix vite.config.ts port from 3690 to 3007 (matches Makefile)
All 6 Zoo ecosystem apps now properly branded and cross-linked.
- Add dedicated product page for RTX PRO 6000 Blackwell GPU ($8,357)
- Move Clusters into Products dropdown menu
- Update navigation to highlight purchasable vs contact sales products
- Add RTX PRO 6000 to Header Products dropdown
- Add route configuration for /rtx-pro-6000
- Include full specs, features, and use cases on product page
- Integrate cart functionality for direct purchase
- Simplified HomePage to: Hero, DGX Spark, Partners, Features, Pricing, CTA
- Created /features page with hardware specs and detailed benefits
- Created /solutions page with use cases, testimonials, and industry solutions
- Updated header navigation to link to Hardware, Solutions, and Clusters
- Streamlined landing page with clear CTA to buy DGX Spark or contact sales
- Improved user journey by organizing content into focused subpages
Change View Hardware button behavior:
- Now scrolls to #dgx-spark section instead of #hardware
- Added id='dgx-spark' to DGXSparkHighlight section
- Provides direct navigation to the purchasable hardware offer
This gives users immediate access to the only directly purchasable
product (DGX Spark) from the hero section.
- Update page title to "Hanzo - On-Demand AI Supercomputing"
- Add comprehensive OpenGraph and Twitter meta tags
- Create OpenGraph image (1200x630) with branded design
- Remove Contact Sales button from header
- Fix horizontal overflow issues:
- Add max-width: 100vw to html/body
- Add overflow-hidden to background container
- Prevent blur elements from causing horizontal scroll
- Add SEO keywords and canonical URL
- Improve social media sharing appearance
Major Updates:
- Full shopping cart with image display and quantity controls
- Stripe checkout integration for DGX Spark ($4,000)
- Sales contact flow for GPU On-Demand and Enterprise products
- 5-item purchase limit enforcement with UI feedback
- Cart persistence using LocalStorage
- Account page with order history
UI Improvements:
- Products dropdown navigation with hover functionality
- Cmd+K search modal with keyboard navigation
- DGX Spark highlight section after hero
- Mobile-responsive design (tested on 375x667)
- Updated branding from "Hanzo.Computer" to "Hanzo"
- Links to Hanzo AI ecosystem in footer
Testing & CI:
- Comprehensive Playwright MCP testing completed
- E2E test suite with 8 test suites covering:
- Full purchase flow
- 5-item limit enforcement
- Sales contact verification
- Navigation and dropdown
- Search functionality (Cmd+K)
- Mobile responsiveness
- Cart persistence
- GitHub Actions CI workflow with:
- Automated E2E tests on all PRs
- Build verification
- GitHub Pages deployment on main branch
Technical:
- React Router v7 for client-side routing
- Stripe Elements for secure payment
- Context API for cart state management
- Tailwind CSS v4 for styling
- TypeScript for type safety
- Playwright for E2E testing
Major Updates:
- Replaced all external NVIDIA image URLs with local high-quality graphics
- Added 25+ professional NVIDIA product and technology images
- Optimized large images (15MB → 223KB for hero images)
Components Updated:
- ImageGallery: Now showcases 12 local images (DGX, H200, Robotics, Quantum, etc.)
- Hero: Uses local DGX SuperPOD background image
- HardwareSpec: Updated all 3 product cards with local images
Infrastructure:
- Added GitHub Actions workflow for automated GitHub Pages deployment
- Configured Vite with proper base path for GitHub Pages
- Added images manifest documentation
Image Assets:
- DGX systems (Spark, Station, SuperPOD)
- H200/H100 GPUs and Blackwell architecture
- RTX Pro workstations and servers
- Technology showcases (robotics, industrial AI, quantum computing)
- Networking (NVLink, silicon photonics, Spectrum)
- Data center and cloud infrastructure
Performance:
- Optimized BFGD KV.jpg: 15MB → 223KB (98.5% reduction)
- All images under 2MB for fast loading
- Lazy loading enabled for gallery images
Ready for deployment to https://hanzoai.github.io/computer/
Sets up the project structure, dependencies, and initial configuration for the Hanzo Computer landing page. This includes:
- Project initialization with Vite and React.
- Configuration for TypeScript, Tailwind CSS, and API key handling.
- Basic HTML structure with meta tags and font links.
- Initial React component structure for the application.
- A placeholder README with local run instructions.
- A placeholder metadata file defining the application name and description.
zeekay