Skip to main content

Screens and navigation

Use this map when adding or editing screens. App.tsx is the source of truth for URL definitions.

Common screens​

URLScreenMain use
/Landing page when signed out; home dashboard after sign-inApp entry point
/videosVideo libraryRegistration, search, and tag organization
/videos/:idVideo detailsPlayback and transcript editing
/videos/coursesCourse listCreating and selecting courses
/videos/courses/:idCourse detailsOrganizing videos, chat, sharing, and analytics
/settingsSettingsProfile, external API keys, and related settings
/pricingPricingReviewing and changing plans
/adminAdministrationUsers, quotas, and reindexing
/share/:tokenShared courseAccessing a shared course
/tryPublic demoAsking the sample course without signing up
/guides / /guides/:slugGuidesPublic articles for course owners
/terms / /privacy / /refund / /legalLegal pagesTerms, privacy, refunds, and the commercial disclosure
/course-invitations/:tokenInvitationReviewing a course invitation

:id and :token are placeholders for actual IDs and tokens.

This is an overview of common navigation. Each screen and the API check login status and access to the target data.

Authentication screens​

URLPurpose
/login / /signupLogin / account registration
/signup/check-email / /verify-emailWaiting for email verification / handling the verification link
/signup/complete / /signup/verifiedReturn pages after a new Google sign-up / a verified email sign-up
/forgot-password / /reset-passwordPassword reset
/change-emailEmail change confirmation
/consentAuthorizing external client access

In the VideoQ app, Japanese generally has no prefix and English uses /en/.... Requests to /ja/... are replaced with the canonical Japanese URL. The documentation site uses a separate convention: English at / and Japanese at /ja/. The on-prem edition omits pricing, legal, guide, sign-up, and public demo pages, and signed-out users enter at login.

Choosing a layout​

  • AppRouteLayout: Ordinary screens share a header; some detail layouts omit the footer.
  • AuthRouteLayout: Authentication-related screens, such as login, registration, and invitations.
  • Shared courses and the public demo: A dedicated screen layout.

Implement only the page body without duplicating the shared header. Handle loading and error displays within the body as well.

Related: Change the frontend, Tests and verification commands.