Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 4 years ago

Responsive Flexbox 3 column layout

Tyson W•305
@Tyson-Wellings
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I am wondering if there is a more efficient way to program the buttons. I gave them a general class but then had to use IDs when styling the individual colours and hover behaviours. I feel like there would be an easier way for this.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nilanshu V Rajmane•125
    @nilanshu96
    Posted about 4 years ago

    Your solution looks pretty good. For button the better solution would be to use the following for hover

    .learn-more-button:hover {
        background-color: transparent;
        color: var(--very-light-gray);
    }
    

    For this to work you need to add a 1px solid white border on the button's class by default so that you won't have to add it separately for hover. Since the border and button's background would have the same color it won't be visible in button's normal state.

  • tediko•6,700
    @tediko
    Posted about 4 years ago

    Hello, Tyson! 👋

    Good effort on this challenge! Everything works good and responds well. In addition to both nilanshu and brasspetals feedback I'd suggest you to take a look at:

    • Change the alt attributes for the .leading-vector-images icon images, as they don't add any extra context for screen reader users. Since your images are decorative your alt text should be provided empty (alt="") so that they can be ignored by assistive technologies.
    • Change width: 300px for your .column-card on mobile to 100%. This way your container will be growing with screen size. Now your solution is only looking good on mobile/desktop.

    Good luck with that, have fun coding! 💪

  • Anna Leigh•5,135
    @brasspetals
    Posted about 4 years ago

    Hi, Tyson! Congrats on submtting another solution! 🎉 It looks good and responds well.

    I'm seconding Nilanshu's solution to the button styling. I do have a small suggestion concerning those buttons, however. They're actually "button-styled links" rather than buttons, as they don't have any button functionality. Switching button out for a tags instead would be more semantically correct. This is a very common mistake, which I've been guilty of myself in the past! 😅

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

Oops! 😬

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

Log in with GitHub