Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@enesozturk
Copy link
Collaborator

Description

Enter the description of this PR and add any important context/info.

Tests

  • - Ran the changes locally with Mintlify and confirmed that the changes appear as expected.
  • - Ran a grammar check on the updated/created content using ChatGPT.

Direct link to the deployed preview files

@github-actions
Copy link

github-actions bot commented Nov 6, 2025

@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

  • appkit/react/early-access/headless.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.

@github-actions
Copy link

github-actions bot commented Nov 6, 2025

@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

  • appkit/react/early-access/headless.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.

@github-actions
Copy link

github-actions bot commented Nov 9, 2025

@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

  • appkit/react/early-access/headless.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.

@github-actions
Copy link

github-actions bot commented Nov 9, 2025

@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

  • appkit/react/early-access/headless.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.

@enesozturk enesozturk changed the title [wip] chore: appkit headless docs chore: appkit headless docs Nov 10, 2025
@github-actions
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

  • appkit/react/early-access/headless.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.

Comment on lines 193 to 199
<Card title="Headless Playground" icon="cubes" href="https://appkit-headless.vercel.app">
You could check our demo app to play around with example Headless implementation
</Card>

<Card title="Source code" icon="github" href="https://github.com/reown-com/appkit" arrow="true">
See the source code of the example Headless implementation.
</Card>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<Card title="Headless Playground" icon="cubes" href="https://appkit-headless.vercel.app">
You could check our demo app to play around with example Headless implementation
</Card>
<Card title="Source code" icon="github" href="https://github.com/reown-com/appkit" arrow="true">
See the source code of the example Headless implementation.
</Card>
<Columns col={2}>
<Card title="Headless Playground" icon="cubes" href="https://appkit-headless.vercel.app">
Check out the demo to play around with the example Headless implementation
</Card>
<Card title="Source code" icon="github" href="https://github.com/reown-com/appkit" arrow="true">
View the source code for the example Headless implementation.
</Card>
</Columns>

I think the doc would look better if we put them in a column of two cards.

@github-actions
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

  • appkit/react/early-access/headless.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.

@github-actions
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

  • appkit/react/early-access/headless.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.

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.

3 participants