Make social sign-in buttons clearer in Boilerplate (#9553)

[msynk]

closes #9553

Summary by CodeRabbit

• UI/UX Improvements
  • Updated social button styling from text to filled variant
  • Modified social buttons layout to distribute space more evenly

[coderabbitai]

Walkthrough

The pull request introduces visual modifications to the social sign-in buttons in the Boilerplate project template. Changes include updating the SocialButton.razor component's button variant from text to filled and adjusting the SocialRow.razor component's BitStack alignment from center to space-between. These modifications aim to enhance button visibility and layout on phone screens.

Changes

File	Change Summary
.../SocialButton.razor	Changed BitButton variant from Text to Fill
.../SocialRow.razor	Modified BitStack alignment from Center to SpaceBetween

Assessment against linked issues

Objective	Addressed	Explanation
Make social sign-in buttons clearer [#9553]	✅
Improve button visibility on phone screens [#9553]	✅

Poem

🐰 Buttons now bold, no longer shy,
Spread wide across the screen so spry!
From text to fill, from center to space,
Social login gets a brand new face!
Hop to it, design with might! 🚀

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/Pages/Identity/Components/SocialRow.razor (1)

4-4: Consider user experience on smaller screens.

Changing the alignment to BitAlignment.SpaceBetween can help visually distribute the buttons across the available space. However, on narrow/mobile screens, the space distribution might cause the buttons to appear cramped at the edges if there is insufficient horizontal space. Consider wrapping the buttons or using responsive breakpoints to ensure consistent user experience across all screen sizes.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4a66fe2 and 14f5b85.

📒 Files selected for processing (2)

• src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/Pages/Identity/Components/SocialButton.razor (1 hunks)
• src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/Pages/Identity/Components/SocialRow.razor (1 hunks)

🔇 Additional comments (1)

src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/Pages/Identity/Components/SocialButton.razor (1)

12-12: Enhance clarity with a filled style.

This change from BitVariant.Text to BitVariant.Fill aligns with making the button more prominent and clear for users. Ensure that this new visual style is tested across various themes and screen sizes to confirm consistent user experience and alignment with branding guidelines.