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

Solution using @media selector

VeyronShark•130
@VeyronShark
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 proud of the fact that I used media selectors for devices of different screen sizes

@media (max-width: 460px){
  article {
    height: 610px;
    min-height: 610px;
  }
}

From next time, I will focus on making the responsiveness more efficient and focus on reducing the number of properties to adjust

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

I add the challenge of making the article size reduce in height, when the screen width reduces. I was trying to reduce the height as a function of the width but it didn't work. What finally worked was using the media selector above to manually reduce the height of the article when the screen size goes below a certain value

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

I would like to know if anybody has a more efficient solution to the screen height problem than me

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ahmed Badr•40
    @ahmed-badr1
    Posted about 2 months ago

    I encountered the same issue and explained its causes in the "Challenges Encountered" section. You can take a look at it.

    Marked as helpful
  • Marzia Jalili•7,270
    @MarziaJalili
    Posted about 2 months ago

    Absolutely Great! 💯

    ✅ You could change the lines below:

    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: center;
    

    To:

    display:  grid;
    place-items: center;
    

    ✅ And about the height, since you've set a fixed height there is no need to repeat yourself by setting min-height. That alone will get the job done for you, bro.

    Other than that the code is neat and clean, keep up the grind!

    😎😎😎

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

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