Skip to content

Correct client portal metadata and trust wording#146

Merged
support371 merged 2 commits into
mainfrom
fix/client-portal-trust-metadata-2026-07-09
Jul 9, 2026
Merged

Correct client portal metadata and trust wording#146
support371 merged 2 commits into
mainfrom
fix/client-portal-trust-metadata-2026-07-09

Conversation

@support371

@support371 support371 commented Jul 9, 2026

Copy link
Copy Markdown
Owner

Purpose

Final production verification found two small portal presentation issues after the main remediation:

  • the page title duplicated the GEM Enterprise suffix;
  • the login screen used unqualified Secure / Encrypted / Monitored badges.

Changes

  • Uses an absolute metadata title to prevent duplicate branding.
  • Keeps the login route no-indexed and no-cached.
  • Replaces “secure account” wording with “authorized account.”
  • Removes unqualified security badges.
  • Adds a practical warning not to share credentials or send identity documents through email or public forms.

No authentication logic or authorization routing is changed.

Summary by Sourcery

Clarify client portal presentation and metadata without altering authentication behavior.

Enhancements:

  • Adjust client login copy to emphasize authorized client and administrator access instead of generic security claims.
  • Replace security badge row with guidance about using only assigned accounts and not sharing credentials or sending identity documents via email or public forms.
  • Refine layout classes for the client login page to improve visual consistency.
  • Set an absolute metadata title for the client login route to avoid duplicated branding and update description to match authorized-access wording.
  • Keep the client login route excluded from indexing and add a no-cache directive in robots metadata.

@vercel

vercel Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
support371-gem-enterprise Ready Ready Preview, Comment, Open in v0 Jul 9, 2026 5:36pm
7 Skipped Deployments
Project Deployment Actions Updated (UTC)
gem-enterprise Ignored Ignored Jul 9, 2026 5:36pm
project-dtrl6 Ignored Ignored Preview Jul 9, 2026 5:36pm
v0-continue-conversation Ignored Ignored Jul 9, 2026 5:36pm
v0-continue-conversation-3875 Ignored Ignored Jul 9, 2026 5:36pm
v0-deployment-alignment-task Ignored Ignored Jul 9, 2026 5:36pm
v0-my-website Ignored Ignored Jul 9, 2026 5:36pm
v0-v0-geraldhoeven-4141-ff89f7f-5 Ignored Ignored Jul 9, 2026 5:36pm

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@sourcery-ai

sourcery-ai Bot commented Jul 9, 2026

Copy link
Copy Markdown

Reviewer's Guide

Updates the client login portal layout metadata and on-page wording to avoid duplicate branding, clarify account authorization, remove unqualified security badges, and add practical credential-handling guidance, while keeping the route non-indexed and non-cached and making minor UI/className tidy-ups.

File-Level Changes

Change Details Files
Adjust login layout metadata to use an absolute title, refine description wording, and strengthen robots directives.
  • Change metadata title to use the absolute form to prevent duplicated site branding.
  • Update metadata description to describe authorized client and administrator accounts more precisely.
  • Extend robots settings to include nocache: true while keeping the route non-indexed and no-follow.
src/app/client-login/layout.tsx
Refine client login page copy and footer guidance to emphasize authorized account usage and safe credential handling.
  • Update the login subtitle text from “secure client or admin account” to “authorized client or administrator account.”
  • Replace the security badges row with a text warning about only using assigned accounts and not sharing credentials or submitting identity documents via email/public forms.
src/app/client-login/page.tsx
Tidy JSX, error messaging, and Tailwind class ordering for the client login page without changing behavior.
  • Add a trailing comma to the default server error string to conform to local formatting style.
  • Reorder container and utility class names for layout, typography, and Button/link styling for consistency and readability.
  • Adjust error message and form field className ordering while preserving visual behavior.
src/app/client-login/page.tsx

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@support371
support371 merged commit 2cd5490 into main Jul 9, 2026
15 of 22 checks passed
@support371
support371 deleted the fix/client-portal-trust-metadata-2026-07-09 branch July 9, 2026 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant