Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
7
Comments
7
Bensolve
@Bensolve

All solutions

  • four-card-feature-section-master using grid


    Bensolve•100
    Submitted about 1 month ago

    I would love feedback on my current approach of combining Grid layout with margin adjustments for staggered positioning. Are there better modern techniques that could make this layout cleaner and more scalable? Suggestions on how to better handle these designs responsively would also be appreciated.


    1 comment
  • product-preview-card-component-main


    Bensolve•100
    Submitted about 1 month ago

    💡 Areas I’d like help with

    I'd appreciate feedback on improving responsive typography (especially multi-line headings), better ways to manage spacing consistency across breakpoints, and how to refine semantic structure for accessibility.


    1 comment
  • Responsive Recipe Page with Semantic HTML & Modern CSS


    Bensolve•100
    Submitted about 2 months ago

    Areas Where I Would Like Help

    • Optimizing Responsive Typography
      I use clamp() and vw units for fluid scaling, but I want feedback on whether my approach balances readability and performance across all devices effectively.

    • Image Breakout Techniques
      I’m using width: 100vw and negative margins for images to break out on mobile. Are there more modern or cleaner methods to achieve this without causing layout shifts or overflow?

    • CSS Architecture & Naming
      I follow a BEM-like naming pattern, but I’d appreciate advice on improving class structure for better scalability and maintainability, especially in larger projects.

    • Semantic HTML Validation
      Would love feedback on my use of semantic elements (main, section, article, heading hierarchy). Are there improvements I can make to boost accessibility or SEO?

    • Handling Edge Cases in Layouts
      Any tips on managing tricky responsive edge cases, like avoiding horizontal scroll on complex nested containers or dynamically sized elements?

    • Performance Best Practices for CSS
      Suggestions on minimizing CSS complexity or improving load/render times without sacrificing design fidelity.


    Feel free to review specific snippets or sections of my code if that helps provide more targeted advice!


    1 comment
  • social-links-profile-main


    Bensolve•100
    Submitted about 2 months ago

    I’d love feedback on these specific areas:

    • Accessibility: Are my focus styles and keyboard navigation done properly?

    • Modern CSS: Am I using current best practices like logical properties, :focus-visible, or :has() correctly?

    • Responsiveness: Do the layout and spacing look good across different screen sizes?

    Any suggestions on how to improve are very welcome!


    2 comments
  • blog-preview-card-main


    Bensolve•100
    Submitted about 2 months ago

    1 comment
  • QR-code-component-solution


    Bensolve•100
    Submitted about 2 months ago

    1 comment
  • QR code component solution


    Bensolve•100
    Submitted about 2 months ago

    I’d appreciate feedback on:

    CSS structure and best practices: Am I using BEM and Flexbox efficiently, or is there a better way to organize the styles?

    Responsiveness: Does the layout hold up well across various screen sizes? Are there improvements I can make?

    Readability of my code: Is my HTML and CSS clean and easy to understand, especially for someone else reading it?

    I’m also open to general tips on improving my workflow or making future components more reusable and scalable.


    0 comments
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub