landing page

Type: noun (compound)
Register: technical, user-facing
Domain: platform-wide

Definition

The base URL route (/) within an app that all inbound traffic sees first. It is where users go by default when they are going to log in. Every user sees the landing page at least once. The landing page lives inside the app — it is a route, not a separate service.

Properties

• Base URL — the / route of the app. The default destination for all traffic.
• All traffic sees it — whether arriving from a shared link, a bookmark, or a direct URL, users land here first.
• Gateway to login — the landing page is where the "Log In" button lives. It funnels users into the Keycloak auth flow.
• Public — visible without authentication. May show program info, schedules, staff, sponsors.
• One per app — each app has exactly one landing page at its base URL.

Why it matters

The landing page is the funnel. It's the one URL Marcus texts to a parent that always works. From there, the user either browses public content or logs in. After login, the app takes over with identity-aware experiences. The landing page is the seam between public and authenticated — it must be inside the app so that login is one click away, not a cross-domain redirect.

Distinguishes from

Term	Difference
app	The app is the complete system. The landing page is one route within it — the public entry point. See definition-app.
dashboard	Dashboards are post-login. The landing page is pre-login (or the redirect target before auth kicks in).
home page	Often used interchangeably, but "landing page" emphasizes the navigational role (where traffic lands), not the content.

Examples

• westsidekingsandqueens.tail5b443a.ts.net/ — Westside app landing page. Shows program info, schedule, staff, sponsors. "Log In" button routes to Keycloak.
• docs.tail5b443a.ts.net/ — pal-e-docs landing page. Shows public notes, search. "Sign In" routes to Keycloak.

Architectural note

board-109 (Split westside-app into westside-landing + westside-app) was scoped when "landing" was considered a separate service. With this definition — landing page is a route inside the app — that split may no longer be the right architecture. The landing page needs to be one click from login. Separating it into a different hostname breaks the auth funnel.

Relations

• contained-by: app
• funnels-to: Keycloak auth flow
• see-also: dashboard (the post-login counterpart)