chore: update LLM.md, standardize CLAUDE.md symlink convention

- LLM.md is the canonical AI context file (tracked in git)
- CLAUDE.md is a local symlink to LLM.md (gitignored)
- Updated LLM.md content for accuracy and conciseness
This commit is contained in:
2026-02-17 18:13:25 -08:00
parent 525394db62
commit 0365e6ffd3
2 changed files with 42 additions and 62 deletions
+2
View File
@@ -22,3 +22,5 @@ dist-ssr
*.njsproj
*.sln
*.sw?
CLAUDE.md
+40 -62
View File
@@ -1,75 +1,53 @@
# Maintenance Report
# hanzo.network
## Recent Changes (2025-06-16)
Marketing site for Hanzo Network, the decentralized AI compute marketplace (hanzo.network). Provides the public-facing site for distributed GPU compute, AI inference, and provider marketplace features.
### Updated Signup Button Styling
- **Issue**: White background signup buttons were not very visible and lacked proper hover states
- **Solution**: Updated all signup buttons across the site to have:
- White background with gray border by default
- On hover: transparent background with white text and white border
- Smooth transition animations
- **Files Updated**:
- `/src/components/pricing/PricingPlan.tsx` - Updated pricing plan buttons
- `/src/components/Products.tsx` - Updated "Get Started Free" button
- `/src/components/navigation/AuthButtons.tsx` - Updated navigation signup button
- `/src/components/navigation/MobileMenu.tsx` - Updated mobile menu signup button
- `/src/components/landing/HeroSection.tsx` - Updated landing page hero button
- `/src/components/pricing/TeamPlanDetails.tsx` - Updated team plan configuration button
## Stack
## Recent Changes (2025-04-07)
- React 18 + TypeScript (Vite 5, SWC)
- React Router v6 (client-side routing)
- Tailwind CSS v4 + Radix UI primitives
- Framer Motion (animations), Three.js (3D)
### 1. Fixed ProductsMenu Import in DesktopNav.tsx
- **Issue**: The ProductsMenu component had both named and default exports, but was imported as a default import in DesktopNav.tsx, causing an error: "lockdown-install.js:1:135422 'http://localhost:8080/src/components/navigation/products-menu/index.tsx' doesn't provide an export named: 'ProductsMenu'"
- **Solution**: Updated the import in DesktopNav.tsx to use a named import for consistency with other menu components.
- **Commit**: Current commit - "Fix ProductsMenu import in DesktopNav.tsx to use named import"
## Structure
```
src/
App.tsx # Root router -- NetworkLanding as homepage
pages/
NetworkLanding.tsx # Homepage (/) -- GPU compute marketplace landing
... # Shared pages (same as other Hanzo sites)
components/ # Shared component library
```
### 2. Fixed ProductsMenu Export/Import Issue
- **Issue**: The ProductsMenu component was exported with a named export but imported as a default export in DesktopNav.tsx, causing a module resolution error: "The requested module doesn't provide an export named: 'ProductsMenu'"
- **Solution**: Added default export to ProductsMenu and updated the import in DesktopNav.tsx to use a default import.
- **Commit**: [fdf6f92](https://github.com/hanzoai/hanzo.ai/commit/fdf6f92) - "Fix ProductsMenu export and update Node.js compatibility"
## Key Routes
### 3. Updated Node.js Version Requirements
- **Issue**: The project required modern JavaScript features (nullish coalescing assignment operator) not supported in Node.js v14.
- **Solution**: Added .nvmrc file specifying Node.js v20 and updated package.json script to suppress warnings.
- **Commit**: [fdf6f92](https://github.com/hanzoai/hanzo.ai/commit/fdf6f92) - "Fix ProductsMenu export and update Node.js compatibility"
- `/` -- NetworkLanding (decentralized compute: GPU marketplace, pricing, provider network)
- All other routes -- Shared product/marketing/account pages from common codebase
## Commands
```bash
pnpm install
pnpm dev # Vite dev server
pnpm build # Production build to dist/
pnpm preview
pnpm lint
```
## Issues Identified
## NetworkLanding Focus
### 1. Component Export/Import Inconsistency (Historical)
- **Issue**: The ProductsMenu component was using a default export while being imported as a named export in DesktopNav.
- **Solution**: Changed ProductsMenu to use named export for consistency with other menu components.
- **Commit**: [68f3e2c](https://github.com/hanzoai/hanzo.ai/commit/68f3e2c) - "Fix: Change ProductsMenu to use named export for consistency"
The homepage highlights:
- Distributed GPU compute (training + inference)
- Cryptographic verification of workloads
- Decentralized P2P infrastructure (no single point of failure)
- Instant scaling (1 to 1000 GPUs)
- Global edge network (sub-100ms latency)
- Provider marketplace (contribute idle compute, set prices)
- Stats: 100K+ GPU hours, 50+ regions, 99.9% SLA, $0.10/GPU-hour
### 2. Node.js Version Compatibility
- **Status**: RESOLVED
- **Issue**: The project required Node.js with support for modern JavaScript features.
- **Solution**: Added .nvmrc specifying Node.js v20 and configured package.json to suppress warnings.
- **Command to use**:
```bash
nvm use
npm run dev
```
## Notes
### 3. Security Vulnerabilities
- GitHub reports 2 moderate security vulnerabilities in the dependencies.
- **Recommendation**: Review and address these vulnerabilities using:
```bash
npm audit fix
# or for a more aggressive approach that might update to new major versions
npm audit fix --force
```
## Project Structure Analysis
- The project is a React application using Vite as the build tool.
- Routing is handled by react-router-dom with separate routes for marketing pages and account pages.
- UI components are organized by feature/page in the components directory.
- The navigation system uses dropdown menus for Products, Solutions, and Resources sections.
## Next Steps
1. Upgrade Node.js to a compatible version (v18+).
2. Run `npm install` to ensure all dependencies are properly installed.
3. Address security vulnerabilities with `npm audit fix`.
4. Continue with feature development or bug fixes as needed.
- Shares the same component library and routes as hanzo.app, hanzo.id, hanzo.one, and sensei.group. Only `NetworkLanding.tsx` and `index.html` metadata are unique.
- No Cloudflare Pages middleware (unlike hanzo.id). Standard static SPA deployment.
- Brand color is cyan (#06b6d4) in the dev console message, vs red for other Hanzo sites.