689-fix: Style issues

[KristiBo]

What type of PR is this? (select all that apply)

• 🍕 Feature
• 🐛 Bug Fix
• 🚧 Breaking Change
• 🧑‍💻 Code Refactor
• 📝 Documentation Update

Description

Related Tickets & Documents

• Related Issue Horizontal scrolling on mobile screens on community page #687, Incorrect width of the Mentors wanted section #689
• Closes Horizontal scrolling on mobile screens on community page #687, Incorrect width of the Mentors wanted section #689

Screenshots, Recordings

Added/updated tests?

• 👌 Yes
• 🙅‍♂️ No, because they aren't needed
• 🙋‍♂️ No, because I need help

Summary by CodeRabbit

• New Features
  • Improved styling flexibility in the About Community component.
• Bug Fixes
  • Enhanced layout responsiveness for the Mentors Wanted section on tablet-large screens.
• Style
  • Updated styles for .mentors-info and .mentors-content to improve layout and scaling.

[github-actions]

Lighthouse Report:

• Performance: 60 / 100
• Accessibility: 99 / 100
• Best Practices: 100 / 100
• SEO: 100 / 100

View detailed report

[SpaNb4]

run visual now

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces minor modifications to the AboutCommunity component and mentors-wanted.module.scss file. In about-community.tsx, the class name assignment for the Image component is updated to use the classNames utility. The SCSS file adjusts the layout and width properties for tablet-large screens, specifically modifying the .mentors-info and .mentors-content classes to improve responsive design.

Changes

File	Change Summary
src/widgets/about-community/ui/about-community.tsx	Updated className to use cx('sloth-mascot') instead of static string
src/widgets/mentors-wanted/ui/mentors-wanted.module.scss	Modified .mentors-info max-width and .mentors-content layout for tablet-large screens

Assessment against linked issues

Objective	Addressed	Explanation
Resolve horizontal scrolling on mobile screens [#687]	❓	Partial styling changes observed, but full resolution unclear without comprehensive testing

Possibly related PRs

• 490-refactor: Widget about home #510: Refactoring of About component to AboutCommunity
• 525-fix: Event card link icon styles #526: Updates to .sloth-mascot class styling
• 522-refactor: Widget community #577: Refactoring of Community component
• 549-refactor: Widget mentors #595: SCSS and class name management refactor
• 550-refactor: Widget mentors wanted #599: mentors-wanted component styling updates
• 551-refactor: Fsd widget merch #670: Widget structure and styling modifications

Suggested labels

high priority

Suggested reviewers

• SpaNb4
• dzmitry-varabei
• ansivgit
• natanchik

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6802e36 and 9d535ba.

📒 Files selected for processing (2)

• src/widgets/about-community/ui/about-community.tsx (1 hunks)
• src/widgets/mentors-wanted/ui/mentors-wanted.module.scss (1 hunks)

🔇 Additional comments (2)

src/widgets/mentors-wanted/ui/mentors-wanted.module.scss (1)

11-11: LGTM! Responsive design improvement

The change from width to max-width improves container fitting behavior on tablet-large screens.

Please verify the visual appearance matches the provided screenshots in the following breakpoints:

src/widgets/about-community/ui/about-community.tsx (1)

41-41: LGTM! Consistent class naming

The change properly utilizes the cx utility for class name binding, maintaining consistency with the project's styling approach.

---

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.

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.