Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Responsive landing page with css flexbox

Aldo Adabunu•310
@KwakuAldo
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I am struggling to make the social media icons change color on hover, I would love some ideas on how to achieve that.

Also, the page doesn't look good on monitors wider than 1440px, do I have to write some more CSS to accommodate wider screens(1440px + screens)?

Any recommendations on what I can improve on are welcome.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fluffy Kas•7,655
    @FluffyKas
    Posted over 3 years ago

    Hiyo,

    Your social icons don't change colour on hover because they're svgs. It's a bit more complicated to style svgs than usual: you need to add them as an inline svg (=>copy-pasting the whole long svg code into your html). Then you can play around with the attribute called "fill". I'd personally say though, this challenge doesn't really call for such complicated methods, being just a junior challenge. For example, I just used Font Awesome icons instead of the svgs given. They're a lot easier to style if you're not very comfortable styling svgs yet and the result is the same or pretty similar! ^_^

    As for your other question, the answer is yes, ideally you accommodate to all screen sizes. If you think about it, often screens are wider than 1440px nowadays! It's an easy fix though. What I'd do is to move the max-width:1440px to the main and then add a margin: 0 auto as well. Also, you could move the footer outside of main. This way you won't need to wrap all the other content in a "main-container" div either.

    There are some bits and bobs to adjust for large screens but I'm sure you can do it, as most of what you done looks great already! Good luck!

    Marked as helpful

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