Nicholai 1be512f658 fix: revert Next.js Image component for Cloudflare Workers compatibility
🐛 Bug Fix:

The Next.js <Image> component requires Node.js APIs that aren't available
in Cloudflare Workers runtime, causing 'Image constructor: new is required' errors.

Changes:
- Revert hero-section.tsx to use background-image CSS
- Revert artists-section.tsx to use native <img> tags
- Add loading='lazy' attributes for native lazy loading
- Keep images.unoptimized: true in next.config.mjs
- Add clear comment explaining Cloudflare compatibility requirement

 What's Still Working:
- All SEO improvements (metadata, Open Graph, Twitter Cards)
- JSON-LD structured data (LocalBusiness, Organization)
- Canonical URLs on all pages
- Font preloading
- Page-specific metadata

Note: Native <img> tags with loading='lazy' provide basic optimization
without requiring Next.js Image APIs. For Cloudflare R2 image optimization,
consider using Cloudflare Images service separately.

Issue: #GH-419 (React error)
Platform: Cloudflare Workers
2025-10-08 19:13:10 -06:00
..
2025-10-06 04:51:57 -06:00
2025-09-16 21:36:20 -06:00
2025-09-16 21:36:20 -06:00
2025-09-16 21:36:20 -06:00
2025-09-16 21:36:20 -06:00
2025-09-16 21:36:20 -06:00
2025-10-07 01:58:10 -06:00
2025-09-16 21:36:20 -06:00
2025-09-16 21:36:20 -06:00