Skip to content

Update WalletKit overview with energetic marketing copy #559

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

devin-ai-integration[bot]
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Jul 11, 2025

Update WalletKit overview with brand-aligned marketing copy

Summary

Updated the first paragraph of the WalletKit overview documentation (/walletkit/overview.mdx) to use more engaging marketing language while maintaining alignment with Reown's brand guidelines for developer documentation. The change evolved through two iterations:

  1. Initial change: Replaced professional copy with very energetic, casual marketing language as originally requested
  2. Brand alignment revision: Updated to professional yet friendly tone after review of Reown brand guidelines

Final content:

Build your wallet into a gateway to onchain apps. WalletKit empowers you to create feature-rich wallet experiences that connect seamlessly with thousands of apps across the onchain ecosystem. Your users deserve intuitive, secure interactions—and with WalletKit's battle-tested infrastructure, you can deliver exactly that. Let's make onchain effortless, together.

Review & Testing Checklist for Human

  • Brand voice verification: Confirm the new tone aligns with Reown's brand guidelines for developer documentation and feels consistent with the rest of the documentation
  • Content appropriateness: Verify the marketing language is suitable for a technical audience while still being engaging
  • Visual rendering: Test how the content appears in the deployed documentation site and ensure proper formatting
  • Value proposition retention: Confirm the new copy effectively communicates WalletKit's core benefits and value
  • Documentation flow: Check that the updated first paragraph flows well with the rest of the overview page content

Recommended test plan: Deploy to preview environment and review the full WalletKit overview page to ensure the new opening paragraph creates appropriate first impressions and maintains documentation consistency.


Diagram

%%{ init : { "theme" : "default" }}%%
graph TD
    A["walletkit/overview.mdx"]:::major-edit --> B["First paragraph<br/>content"]:::major-edit
    A --> C["Rest of overview<br/>(Quickstart, Features)"]:::context
    B --> D["Brand guidelines<br/>review"]:::context
    B --> E["Final marketing copy<br/>(professional + engaging)"]:::major-edit
    
    subgraph Legend
        L1[Major Edit]:::major-edit
        L2[Minor Edit]:::minor-edit  
        L3[Context/No Edit]:::context
    end
    
    classDef major-edit fill:#90EE90
    classDef minor-edit fill:#87CEEB
    classDef context fill:#FFFFFF
Loading

Notes

  • This change only affects the introductory paragraph - all other content (quickstart guides, features, etc.) remains unchanged
  • The content went through two iterations: initially very casual/energetic per request, then revised to align with brand guidelines
  • The revision addresses specific brand guideline violations: removed buzzwords, fear-based messaging, and overly casual language
  • Maintains WalletKit's core value proposition while improving engagement over the original professional copy
  • Requested by rohit@reown.com (@rohit-710)
  • Link to Devin run: https://app.devin.ai/sessions/03fb9ec37013418cb8182d7533d99398

Replace the first paragraph with more enthusiastic and engaging language
to better capture user attention and excitement about WalletKit features.

Co-Authored-By: rohit@reown.com <rrohitramesh710@gmail.com>
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Copy link

@devin-ai-integration[bot] Please review the tone of voice for the content changes in this PR against Reown's brand guidelines.

📝 Content Review Request

Files to review: 1

  • walletkit/overview.mdx

Review focus:

  • Tone alignment with Reown's brand guidelines
  • Clear and accessible language for developers
  • Professional yet approachable communication
  • Consistent terminology usage

Guidelines summary:

  • Clear & Accessible: Translate complex ideas into approachable language
  • Professional yet Friendly: Maintain authority while being welcoming
  • Developer-Focused: Understand technical audience but remain inclusive
  • Avoid: Overly casual language, fear-based messaging, buzzwords, jargon without explanation
  • Embrace: Clear explanations, confident tone, transparency, respectful communication

Please analyze the content changes and provide constructive feedback on tone and voice alignment.

@rohit-710
Copy link
Member

@devin-ai-integration[bot] Please review the tone of voice for the content changes in this PR against Reown's brand guidelines.

📝 Content Review Request

Files to review: 1

  • walletkit/overview.mdx

Review focus:

  • Tone alignment with Reown's brand guidelines
  • Clear and accessible language for developers
  • Professional yet approachable communication
  • Consistent terminology usage

Guidelines summary:

  • Clear & Accessible: Translate complex ideas into approachable language
  • Professional yet Friendly: Maintain authority while being welcoming
  • Developer-Focused: Understand technical audience but remain inclusive
  • Avoid: Overly casual language, fear-based messaging, buzzwords, jargon without explanation
  • Embrace: Clear explanations, confident tone, transparency, respectful communication

Please analyze the content changes and provide constructive feedback on tone and voice alignment.

Devin, please review the content change as per the tone of voice document and update the PR accordingly

Update the first paragraph to follow Reown's professional yet friendly
tone guidelines for developer documentation. The new copy is:
- Professional and respectful of developers' time
- Clear and accessible without buzzwords
- Confident but approachable
- Empowering and collaborative
- Avoids fear-based messaging and overly casual language

Co-Authored-By: rohit@reown.com <rrohitramesh710@gmail.com>
Copy link

@devin-ai-integration[bot] Please review the tone of voice for the content changes in this PR against Reown's brand guidelines.

📝 Content Review Request

Files to review: 1

  • walletkit/overview.mdx

Review focus:

  • Tone alignment with Reown's brand guidelines
  • Clear and accessible language for developers
  • Professional yet approachable communication
  • Consistent terminology usage

Guidelines summary:

  • Clear & Accessible: Translate complex ideas into approachable language
  • Professional yet Friendly: Maintain authority while being welcoming
  • Developer-Focused: Understand technical audience but remain inclusive
  • Avoid: Overly casual language, fear-based messaging, buzzwords, jargon without explanation
  • Embrace: Clear explanations, confident tone, transparency, respectful communication

Please analyze the content changes and provide constructive feedback on tone and voice alignment.

Copy link
Contributor Author

Brand Guidelines Analysis & Content Revision

Thank you for the brand guidelines review request. I've analyzed the initial content against Reown's tone of voice framework and made the necessary revisions.

Initial Content Issues

The original energetic copy violated several key brand guidelines:

  • Overly casual language: "OMG", "INSANE", "EPIC" - too informal for developer documentation
  • Fear-based messaging: "Don't get left behind" creates unnecessary urgency/fear
  • Buzzwords without substance: "FIRE", "INSANE", "EPIC" don't provide clear value
  • Disrespectful tone: "Stop being a noob" is not respectful of developers' expertise
  • Lack of professionalism: Overall tone was too casual for technical documentation

Revised Content Alignment

The updated content now follows Reown's guidelines for developer documentation:

  • Professional yet friendly: Maintains authority while being welcoming
  • Clear & accessible: Translates value proposition into approachable language
  • Developer-focused: Respectful of technical audience and their time
  • Empowering tone: "WalletKit empowers you" rather than fear-based messaging
  • Collaborative approach: "Let's make onchain effortless, together"
  • Confident without arrogance: States benefits clearly without buzzwords

Final Content

Build your wallet into a gateway to onchain apps. WalletKit empowers you to create feature-rich wallet experiences that connect seamlessly with thousands of apps across the onchain ecosystem. Your users deserve intuitive, secure interactions—and with WalletKit's battle-tested infrastructure, you can deliver exactly that. Let's make onchain effortless, together.

This revision maintains the goal of more engaging content while adhering to the "informative, professional, straightforward, helpful and respectful" tone specified for developer documentation in the brand guidelines.

The changes have been committed and pushed to the PR branch.

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