Skip to content

feat(reference-app): style the pages with Pico and make the consent screen realistic - #191

Closed
ardetrick wants to merge 3 commits into
mainfrom
feat/reference-app-styling-pico
Closed

feat(reference-app): style the pages with Pico and make the consent screen realistic#191
ardetrick wants to merge 3 commits into
mainfrom
feat/reference-app-styling-pico

Conversation

@ardetrick

Copy link
Copy Markdown
Owner

Restyles the reference app's login, consent, logout, callback, tokens, and landing pages with vendored Pico CSS (v2.1.1) as a clean centered card, and reworks the content so the pages read like a real client would build them.

Highlights:

  • Consent now names the requesting client and describes each scope in plain language ("Confirm your identity (openid)"), sourced from the consent challenge, instead of listing raw scope tokens. The redundant offline scope is dropped.
  • The callback page leads with a prominent "Exchange code for tokens" button and an honest note that a real app does this server-side; the raw code and client credentials move into disclosures. The tokens page leads with a success line and tucks the raw response and decoded claims away.
  • Login pre-fills the demo credentials with a caption so they are obvious.
  • Screenshots are pinned to a uniform 576x520 frame, and collapsing the variable-length content makes every screen a fixed, deterministic size (ready for a future slideshow/gif).

Split into three reviewable commits (Pico styling / collapse variable content / consent enhancement), each building green on its own.

Known follow-up: the three "after-consent-submit" images are still the functional tests' echo-endpoint captures (a random code, unstyled). A later change will re-source the README walkthrough from the /demo flow, replacing them with the styled, deterministic callback and tokens pages.

…g pages

Vendors Pico v2.1.1 as static/pico.min.css and restyles the pages as a centered card. Login now pre-fills the demo credentials with a caption so they are obvious. Page titles are normalized to h1, and the screenshot viewport is pinned to 576x520 so captures are a uniform, GitHub-column-friendly size.
…sures

The callback page leads with a prominent Exchange button and an honest note that a real app does this server-side; the raw authorization code and the client credentials move into <details> disclosures. The tokens page leads with a success line and tucks the raw token response and decoded claims behind disclosures. This keeps the variable-length, non-deterministic content out of the default view so every screen is a fixed size.
…n consent

The consent screen now reads like a real client's: it names the requesting application and shows a plain-language description for each scope (with the raw scope name alongside), sourced from the consent challenge. Adds a RequestedScope catalog for the descriptions. Drops the redundant 'offline' scope, and gives the test clients a stable client_name so the screen is deterministic. Regenerates the README screenshots.
@ardetrick

Copy link
Copy Markdown
Owner Author

Superseded by three stacked single-commit PRs so each lands as its own squash commit.

@ardetrick ardetrick closed this Jul 26, 2026
@ardetrick
ardetrick deleted the feat/reference-app-styling-pico branch July 26, 2026 04:01
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