Skip to content

Public site

These components draw the pages anyone can open without signing in: the landing page, the legal pages, the Help Center and the sign-in screens.

The landing page is src/app/(public)/page.tsx, and its parts are in src/components/landing. It stacks one section per block. The text lives in messages/<language>.json under landing. src/constants/landing.ts keeps only the ids, links, icons and order of the items, such as the questions, use cases and footer links.

Component File What it does
LandingHeader header/landing-header.tsx The top bar that stays in place. It links to the page’s sections, marks the one on screen (useActiveLandingSection), and has a phone menu and the sign-in and sign-up buttons.
HeroSection hero/hero-section.tsx The first screen: the headline, the line under it, the buttons and the background picture.
ProblemSection problem/problem-section.tsx A short statement of the problem ianua solves.
WhyIanuaSection why-ianua/why-ianua-section.tsx “Why not just keep gluing tools together”, as numbered reasons drawn with ReasonCard.
ReasonCard why-ianua/reason-card.tsx One numbered reason: number, title, description.
HowItWorksSection how-it-works/how-it-works-section.tsx “Every request takes …”: the path of a request as numbered steps.
StepCard how-it-works/step-card.tsx One step: number, title, description, and a line to the next unless it is the last.
StepIcon how-it-works/step-icon.tsx The marker and line StepCard draws.
WhatYouGetSection what-you-get/what-you-get-section.tsx The grid of features, “The complete picture”.
FeatureCard what-you-get/feature-card.tsx One feature: title, description, and a picture if there is one.
AiAgentsSection ai-agents/ai-agents-section.tsx How ianua governs AI agents, laid out with AiAgentCard.
AiAgentCard ai-agents/ai-agent-card.tsx One thing ianua does for agents: icon, title, description. size and tall set how much of the grid it takes.
SecuritySection security/security-section.tsx The list of security promises, made of SecurityCard.
SecurityCard security/security-card.tsx One security promise: icon, title, description.
UseCasesSection use-cases/use-cases-section.tsx The use cases, from USE_CASES in constants/landing.ts, which holds only ids. The text is in the message files.
FaqSection faq/faq-section.tsx Common questions that open one at a time.
ContactSection contact/contact-section.tsx A contact form (name, email, company, message), checked with createContactSchema in schemas/contact-schema.ts in the visitor’s language. Sending is not built yet: handleMockSubmit only shows the “sent” state.
LandingFooter footer/landing-footer.tsx The footer: logo, optional links to the sections, and the legal bar.
FooterLegalBar footer/footer-legal-bar.tsx The legal and Help Center links, from LANDING_LEGAL_LINKS. The landing, legal and sign-in footers share it. Links open in a new tab, except on a legal page.
LandingSectionLink shared/landing-section-link.tsx A link that scrolls smoothly to a section, leaving room for the top bar.
LandingHorizontalScrollContainer shared/landing-horizontal-scroll-container.tsx Rows of cards that scroll sideways on small screens.
ScrollReveal shared/scroll-reveal.tsx Fades or slides its content in as it comes on screen, after an optional delay.
ScrollStatusIndicator shared/scroll-status-indicator.tsx A decoration that follows how far down the page the visitor is.
SectionBadge shared/section-badge.tsx A small label with an icon, above a section’s heading.
StatusDivider shared/status-divider.tsx A line between sections with a label on it.

These are in src/components/legal.

Component File What it does
LegalHeader legal-header.tsx The top bar of /privacy-policy and /terms-of-use, with links between them and a phone menu. The pages’ text is in messages/<language>.json under legal.
LegalSection, LegalParagraph, LegalProse, LegalList, LegalBullet, legalRichTags legal-prose.tsx The parts both legal pages are made of. legalRichTags are the tags used in the legal messages: <mail>, <privacy>, <highlight> and <brand>. constants/legal.ts keeps the contact address, the date of the last change, and the ids of the table rows and lists. A translated page says the English version applies if the two differ.

The Help Center is at /help-center/..., and its parts are in src/components/help-center. It shows the articles in src/constants/help-center.ts. Each article is made with article({ slug, title, lastUpdated, intro, sections, subArticles? }). A section holds blocks of the kinds paragraph, list, steps or callout. The helpers that find articles, such as getHelpArticleHref and getAdjacentHelpArticleRefs, sit next to the content.

Component File What it does
HelpCenterHeader help-center-header.tsx The top bar: logo, the path to the current article, and the phone menu.
HelpCenterSidebar help-center-sidebar.tsx The tree of categories and articles, with a search filter. On a computer it is a fixed sidebar. On a phone it sits in the menu (variant).
HelpCenterArticle help-center-article.tsx One article: title, date of the last change, intro, sections and their blocks, and links to the articles before and after.
HelpCenterToc help-center-toc.tsx “On this page”: the article’s contents, with the part on screen marked (useActiveHelpSection).
HelpCenterFeedback help-center-feedback.tsx “Was this helpful?” with yes and no buttons. Nothing is sent.

These are in src/components/auth. The organization’s sign-in (/login) and each tenant’s (/organizations/{org}/tenants/{tenant}/login) both use them. A form knows which one it serves by whether it was given orgSlug and tenantSlug.

Component File What it does
AuthLayout AuthLayout.tsx The frame of the sign-in screens: top bar, background and an optional footer. It sends someone already signed in to the dashboard, unless told not to (skipAuthenticatedRedirect). Its Sign Up link shows only when the installation takes sign-ups (useSignupOpen), and a self-hosted one does not.
AuthCard AuthCard.tsx The card in the middle that holds a form: icon, title, the line under it, and an optional “back to login” link.
LoginForm login-form.tsx Sign-in in two steps: email, then password. It offers passkeys, by button and as the browser fills in the email. On a tenant’s page it also offers a mailed link, single sign-on and self sign-up, as the tenant allows. It hands over to the second-factor check or its setup when the API asks, and offers “Trust this device”.
MfaVerificationStep mfa-verification-step.tsx Asks for a 6-digit code, or a recovery code, when a sign-in needs a second factor. Works for both kinds of session.
MfaEnrollmentStep mfa-enrollment-step.tsx Shown when a tenant needs a second factor and the person has none. It shows a QR code, confirms a code, shows the recovery codes, and then opens the tenant.
DuePasswordChangeStep due-password-change-step.tsx Asks for a new password when a tenant sign-in’s password was set by an administrator or has expired. With a second factor it also asks for a code.
MailedPasswordChange mailed-password-change.tsx Where the mailed link for such a change lands (/change-password).
SignupConfirmation signup-confirmation.tsx Where the sign-up confirmation mail lands (/signup/confirm). It creates the organization once.
RecoveryCodes recovery-codes.tsx Shows a new second factor’s recovery codes, once.
TenantSignInCompletion tenant-sign-in-completion.tsx Finishes, exactly once, a sign-in that left the sign-in page, even when React draws it twice. Then it opens the tenant, or asks for a second factor or its setup. The two pages below share it.
MagicLinkCompletion magic-link-completion.tsx Where a mailed sign-in link lands. It uses the token through TenantSignInCompletion.
SignInConfirmation sign-in-confirmation.tsx Where the link that confirms a sign-in from a new device lands. It finishes the sign-in this browser kept, for an organization member or a tenant user.
SsoCompletion sso-completion.tsx Where single sign-on comes back. It trades the one-time ?code= through TenantSignInCompletion. If the identity provider reported no second factor and the tenant wants one, it asks for it.
SamlBrowserStep saml-browser-step.tsx The pages the platform sends a browser to for SAML: gets the signed answer and posts it to the app or identity provider. Signs Pat in first when the page needs a session.
OAuthConsent oauth-consent.tsx An app’s OAuth sign-in: asks the platform what the request needs, signs Pat in or asks her to agree to the scopes, then hands the answer back to the app.
OAuthLogout oauth-logout.tsx An app’s OAuth sign-out: asks to confirm when the app did not name Pat, then tells the other apps and leaves.
OrgSsoCompletion org-sso-completion.tsx Where the organization’s identity provider answers. Finishes the sign-in, asking for a second factor when the organization wants one.
WorkflowApproval workflow-approval.tsx The page a chat message’s Approve and Deny buttons open. Shows the data and decides it; nothing is decided by the press in the chat.
SetPasswordForm set-password-form.tsx A password and its repeat, checked against the password rules with live hints, and an optional terms box. Accepting an invitation and resetting a password use it.
TenantSignUpForm tenant-sign-up-form.tsx Self sign-up for a tenant (name, email, password) when the tenant allows it. Otherwise it says “Sign-up is closed”.
SocialButton SocialButton.tsx A provider button (Google, GitHub, passkey) with a loading state.
TokenStatusScreen, CheckingLinkScreen, ExpiredLinkScreen, AlreadyUsedLinkScreen, InvalidLinkScreen, ResendLinkAction, LinkStateAction token-status-screens.tsx The shared screens of mailed links (verify email, invitations, resets): checking, expired, already used and not valid, with their resend and next-step buttons.

IntegrationConnected (components/auth/integration-connected.tsx) is where a service sends the browser back after signing in. It clears the address, finishes the connection with the one-time code, then opens Connected accounts; a failure says why with Try again.