Skip to content

feat(portal): mark UI as testing-only, not for production#40

Open
atsyplikhin wants to merge 1 commit into
feat/registry-paginationfrom
portal/testing-only-banner
Open

feat(portal): mark UI as testing-only, not for production#40
atsyplikhin wants to merge 1 commit into
feat/registry-paginationfrom
portal/testing-only-banner

Conversation

@atsyplikhin
Copy link
Copy Markdown
Collaborator

Summary

  • Adds an amber "Testing version only" banner above the logo on login.html, signup.html, and auth/cli_approve.html.
  • Adds a "TESTING ONLY — NOT FOR PRODUCTION" pill next to the "Device Connect" logo in base.html, so the warning shows on every authenticated page (dashboard, devices, coding agents, admin).

Stacked on top of #38 — base is feat/registry-pagination. Merge #38 first; this PR will retarget to main automatically.

Test plan

  • Visit /login — verify the amber banner renders above the indigo logo card.
  • Visit /signup — verify the banner renders.
  • Hit the CLI approve flow (/auth/cli/...) — verify the banner renders.
  • Sign in and visit /dashboard, /devices, /coding-agents, and the admin pages — verify the amber "TESTING ONLY — NOT FOR PRODUCTION" pill renders next to the Device Connect logo in the top nav on each page.

🤖 Generated with Claude Code

Add an amber "Testing version only" banner to the login, signup, and
CLI-approve pages, and a "TESTING ONLY — NOT FOR PRODUCTION" pill next
to the Device Connect logo in the post-login nav so the warning is
visible on every authenticated page.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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