zeekayandHanzo Dev 5d48e529c7 Render the real landing page and serve it from a Cloudflare Worker ...

The site shipped every content block and every renderer component, but
src/app/page.tsx was a "Coming soon" stub, so none of it was reachable. DNS
also still pointed at GitHub Pages, which served nothing -- the domain was dark.

- Restore the landing page (intro, products, leadership, advisors, partner
  logos, press, outro) from the composition in luxfi/web, whose src tree is
  byte-identical to this one outside src/app.
- next.config.js: wire up MDX and the SVGR webpack config the repo already
  carried but never referenced.
- Bypass the @luxfi/ui package barrel for <Main> and <Footer>. The barrel also
  re-exports the auth panels, which drag Firebase into the graph and abort
  `output: 'export'` with auth/invalid-api-key. A static marketing page needs
  no auth.
- Render <Footer> inside a client boundary: it passes an `itemClx` *function*
  to <NavItems>, which a Server Component may not do.
- Own the layout instead of @luxfi/ui's RootLayout (same reason: it mounts the
  Firebase auth + commerce providers). Load Lux colors, global styles and the
  Inter/Druk Wide faces via the supported non-next path.
- Bump @hanzo/ui 5.3.22 -> 5.3.34, @hanzo/commerce 7.3.8 -> 7.3.10 and
  @luxfi/ui 5.5.2 -> 5.5.3, matching the versions luxfi/web builds against.
  @hanzo/auth stays at 2.5.5; 2.5.8 does not parse (`type App` inside a
  destructuring pattern).
- Name Lux Industries Inc as the legal entity in the footer and author
  metadata.
- Add wrangler.toml so the built export is served by a Worker on lux.partners
  and www.lux.partners.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-05 15:59:40 -07:00

843 KiB

Raw Permalink History

View Raw