feat(heroes): credential cards, wallet phone, certified Proof-of-Trust, theme fix - #47
Merged
Merged
Conversation
The server no longer renders data-theme="dark" on <html>: a client-side navigation between locales re-rendered the attribute without re-running the pre-paint theme script, so a light theme flipped to dark. The language switch is now a full navigation, so the proxy records the NEXT_LOCALE cookie and redirects to the canonical path instead of leaving /en/... in the address bar.
Replaces the Proof-of-Trust panel with a fan of three fictional verifiable credentials drawn like the Verana Playground event tickets: a citizen identity, a business registration and the Verana Certified Integrator credential Mobiera issues. Line-art scenes in currentColor, brand gradients, translated labels, a caption that says every name is fictional.
Design C: a phone running a fictional wallet at the moment of trust. A demo bank asks to connect, the wallet shows its Proof-of-Trust checked against the Verana registry and the credential it asks for, with Share and Decline; a credential-received notification overlaps the top. Thin bezel, scaled to 85 percent, pure markup and CSS in the site's tokens, translated. The hero becomes two columns like the home page.
Home screen with the three example credentials stacked as cards, recent activity and a tab bar, replacing the connection-request screen.
…hero Design C: what a customer's wallet shows when it meets a certified integrator. The company's DID resolving, its organization and service credentials, and the Verana Certified Integrator line highlighted, issued by Mobiera and valid, with a chip for the directory generated from the Trust Graph. Example data, labelled as such, translated. Reuses the Proof-of-Trust panel styles; the hero becomes two columns like the other pages.
feat(certification): Proof-of-Trust of a certified integrator in the hero
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why this PR exists
PRs #42, #43 and #44 were chained on
feat/spanishand merged into their base branches, not intomain(GitHub only retargets a PR when its base branch is deleted, andfeat/spanishwas kept). The theme fix pushed tofeat/spanishafter #41 merged was left behind the same way. This branch starts frommain(after the 1.7.0 release and the honeypot fix #45) and merges that chain in, so nothing is rewritten and the nine commits keep their history:Verified on the merged result
No conflicts. Type-check, unit tests, en/es key parity, full build. Standalone server:
/,/trust,/certification, their/esversions and/contactanswer 200; the three hero components render and the honeypot fix from #45 (hp_check,elapsed_ms) is intact.After merging, the branches
feat/spanish,feat/hero-credential-cards,feat/trust-phoneandfeat/certification-proofcan be deleted.