Reflect whitelabel cross-app reality across login docs#5
Merged
Conversation
VeChain Kit v2.7+ ships a whitelabel cross-app popup (connect.vechain.org / cross-app-connect/) that handles Google / Apple / X / Discord / GitHub / TikTok / LINE OAuth without the consuming dApp owning a Privy account. Update the docs that still framed Privy as required for social login. - connection-types.md: rewrite the "Privy Cross App" section to describe the whitelabel as VeChain-branded, free, smart-contract- aware, and the default in v2.7+. List the actual benefits instead of just "you can have social login without paying Privy". - quickstart/setup-privy-optional.md: add a hint at the top spelling out that Privy is now genuinely optional, and rewrite the pros/cons hint to reflect what self-hosting actually unlocks today (email/passkey/SMS, custom OAuth, in-dApp branding, no popup per signature). - quickstart/provider-configuration.md: split the loginMethods reference into "OAuth works without your own Privy" vs "requires your own Privy" groups; reframe the Privy Integration section as opt-in for advanced needs only. Both the GitBook publish copy (root) and the docs/ working copy are updated in lockstep.
10 tasks
The kit just gained a per-entry `isPrimary?: boolean` on loginMethods (vechain-kit PR #620). Mark any visible button as the recommended CTA — filled inverted surface + green dot — instead of the previously hardcoded VeWorld treatment. When no entry sets it, the kit falls back to highlighting the first visible method. Updates: - `docs/quickstart/login-customization.md`: new "Recommended primary CTA — `isPrimary`" subsection under "Configuring the grid", with two side-by-side examples (implicit fallback vs. explicit). Notes which buttons currently support the filled treatment (veworld / google / apple / github). Updated the v2.7 changelog blurb at the top to mention dev-controlled emphasis. - `docs/quickstart/provider-configuration.md` (+ root GitBook copy): example loginMethods now shows `isPrimary: true`, and the reference-list intro explains the flag + fallback behavior.
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.
Summary
VeChain Kit v2.7+ ships a whitelabel cross-app popup (
connect.vechain.org/cross-app-connect/in the kit repo) that handles Google / Apple / X / Discord / GitHub / TikTok / LINE OAuth without the consuming dApp owning a Privy account. The docs still framed Privy as required for these methods.Changes
connection-types.md(root +docs/GitBook copy): the "Privy Cross App" section is rewritten as Privy Cross App (VeChain whitelabel). Lists real benefits instead of just "you can have social login without paying Privy" — free social login, one identity across the ecosystem, VeChain-branded popup with 17 languages, smart-contract-aware transaction review ("Send 10 B3TR to vechain.vet" instead of raw hex), auto-recovery from stale sessions.quickstart/setup-privy-optional.md(both copies): success hint at the top spelling out that Privy is now genuinely optional. Pros/cons rewritten to reflect what self-hosting Privy actually unlocks today (email / passkey / SMS, custom OAuth providers, in-dApp branding, no popup per signature).quickstart/provider-configuration.md(both copies): split theloginMethodsreference into "works without your own Privy" (Google, Apple, Twitter, Discord, GitHub, TikTok, LINE) and "requires your own Privy" (email, passkey, SMS) groups. The "Privy Integration (Optional)" section is reframed as opt-in for advanced needs only.Related
cross-app-connect/host this doc describes)Test plan
connection-types.md🤖 Generated with Claude Code