Right now your portal redirects every visitor straight into the auth provider's login screen because there's no public route. That's a rough first impression — visitors land on a screen that says "sign in" without any explanation of what they're signing into. A small structural change fixes that:
- Public landing page at
/— explains what the portal is, with a "Sign in" CTA. - Everything else protected — docs, API references, etc. are gated behind
protectedRoutes.
This way, unauthenticated visitors get a real homepage, and clicking "Sign in" (or any protected link) sends them through your auth provider with a return URL back to the page they wanted. We're also shipping a related fix soon (PR #2398) that removes an extra "login or register?" dialog and goes straight to the auth provider — together with the homepage, this gives a much cleaner flow.