fix: Enable button clicks on mobile coming soon page

[sethwebster]

Summary

• Fixed button interaction issues on mobile devices on the coming soon page
• 3D React logo canvas was blocking touch events
• Added pointer-events-none to logo container
• Improved button responsiveness with better mobile padding

Changes

• Added pointer-events-none class to ReactLogo3D container div
• Made buttons more mobile-friendly with responsive padding and text sizes

Test Plan

• Test button clicks on mobile devices (iOS Safari, Android Chrome)
• Verify 3D logo still animates correctly
• Confirm GitHub sign-in button works on mobile
• Verify "Request Access" button works on mobile

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
react-foundation	Error			Oct 23, 2025 0:19am

[claude]

Code Review - PR #15

Summary

This PR addresses mobile button interaction issues and introduces a comprehensive theming system. While the core fix is solid, there are several critical concerns.

Positive Aspects

1. Mobile fix is correct - pointer-events-none properly prevents canvas from blocking touch
2. Theming architecture is well-designed with clean separation of concerns
3. Comprehensive documentation with excellent THEMING_GUIDE.md

Critical Issues

1. Major Version Bump: Next.js 15 to 16

• Next.js 16 is a major version with breaking changes
• NOT mentioned in PR title or description
• Recommendation: Separate into its own PR with proper testing

2. Scope Creep

• 90+ files modified (3,323 additions, 896 deletions)
• PR says it fixes mobile buttons but includes massive theming refactor
• Actual mobile fix is ~5 lines, remaining 3,300+ lines are theming work
• Recommendation: Split into two PRs

3. Incomplete Implementation

• Despite theming system, many hardcoded colors remain in coming-soon/page.tsx
• Lines 74, 105, 111, 119, 127, 143, 147, 156 have hardcoded cyan/orange/amber
• Recommendation: Fully migrate or document exceptions

Other Concerns

• Test plan checkboxes all unchecked
• Vercel build FAILED
• Theme config duplication (theme.ts vs theme-config.ts)
• Debug file committed (debug-theme.html)
• No test coverage
• Accessibility concerns with contrast ratios

Security

No security concerns identified

Performance

Minor concerns with theme switching and hydration. Consider using next-themes library.

Recommendations

CRITICAL:

• Separate Next.js 16 upgrade into own PR
• Fix Vercel build failures
• Split into two PRs (mobile fix + theming)

HIGH:

• Complete test plan

MEDIUM:

• Consolidate theme configs
• Fix or document hardcoded colors

Score: 6.5/10

• Mobile Fix: 9/10
• Theming System: 6/10
• Testing: 2/10
• Scope Management: 3/10
• Security: 10/10

Verdict: Request Changes

The mobile fix is excellent but bundling it with massive theming refactor and Next.js 16 upgrade makes this too risky.

Suggested path:

1. Create minimal PR with just pointer-events-none fix
2. Merge quickly (blocking mobile users)
3. Continue theming work in separate PR
4. Separate PR for Next.js 16 upgrade

---

Claude Code Review - following CLAUDE.md guidelines