Member Junction
    Preparing search index...

    One card on the login screen — a trust mark, a support route, a policy link, a feature note.

    Cards exist so that content a deployment wants to add does not require an Angular template: a per-tenant branding record or an environment file can carry this array. Anything richer than a card projects into the matching slot instead, which suppresses the cards for that region (documented on the slots themselves).

    interface MJLoginCard {
        href?: string;
        icon?: string;
        newTab?: boolean;
        region?: MJLoginCardRegion;
        text?: string;
        title: string;
    }
    Index

    Properties

    href?: string

    Makes the card a link. Angular sanitizes the bound URL, so a javascript: href from configuration is neutralized rather than executed.

    icon?: string

    Font Awesome class for the leading icon, e.g. 'fa-solid fa-shield-halved'. MJ uses Font Awesome throughout; omit for a card with no icon.

    newTab?: boolean

    Opens href in a new tab — usually what a policy or support link wants, so the half-finished sign-in is not navigated away from. Implies rel="noopener noreferrer".

    Which region the card renders in. Defaults to 'panel' — beneath the sign-in options.

    text?: string

    Supporting line under the title.

    title: string

    The card's heading. The one required field — a card with no title has nothing to say.