Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 months ago

Responsive design with FLexbox

RenBear•60
@RenBear
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am most proud of how the responsive design turned out. It was challenging to ensure the site displayed properly on various devices, but I spent a lot of time fine-tuning the media queries and testing across different screen sizes. The final product is visually appealing, and I was able to create a seamless experience for both desktop and mobile users.

What challenges did you encounter, and how did you overcome them?

ne of the major challenges I encountered was ensuring that the layout was truly responsive across different devices and screen sizes. I had to adjust my approach several times, especially when testing the site on smaller mobile devices. I overcame this by refining my media queries and using flexible units like percentages for width and em for font sizes. Another challenge was ensuring cross-browser compatibility. At times, certain CSS properties didn’t render as expected in browsers like Safari. To solve this, I researched browser-specific solutions and implemented vendor prefixes where needed, ensuring consistent styling across browsers. Finally, I focused on optimizing images and layout for mobile to ensure fast loading times, which was crucial for performance

What specific areas of your project would you like help with?

I'm looking for help in a few areas: First, I would appreciate more guidance on advanced layout techniques like Flexbox and CSS Grid, as I’d like to better understand how to use these for more complex, responsive layouts. I’d also love some advice on improving cross-browser compatibility, especially when using newer CSS features. Lastly, if possible, I'd like some feedback on performance optimization, particularly for mobile users, as I want to ensure fast load times and a smooth user experience

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on RenBear's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
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

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.