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

3 Column Display using HTML & CSS FlexBox

ShantanuBorkar•80
@AlsoShantanuBorkar
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


How do I make the code smaller?

One way is to make a common hover property for the buttons but then I will not be able to customize the individual colors for the buttons, so is there any other way for me to do it?

Any feedback is appreciated... Thanks.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted over 3 years ago

    Hi there! 👋

    Congratulations on finishing this challenge! 👏

    I have some feedback on this solution:

    • Accessibility
      • Wrap all of the page content with main tag,except the attribution. The attribution should live outside the main element.
    <body>
      <main>
        page content goes here...
      </main>
      <footer class="attribution">
          attribution links goes here...
      </footer>
    </body>
    
    • I agree with @Samadeen that headings must be in a logical order. Heading tags can be used by users of assistive technology to navigate the website. If headings are not in a logical order, those users might get confused.
    • In this case, make all h2 to h3. You could add a visually hidden h1 if you want.
    • Use CSS to uppercase the text. The uppercased word in the HTML will be spelled by the screen reader (spelled letter by letter)
    • I would use link elements for the Learn more buttons. Do you have any reasons for using button elements instead of link elements?
    • Create a custom :focus-visible styling to any interactive elements (button, links, input, textarea). This will make the users can navigate this website using keyboard (by using Tab key) easily.
    • Anyway, always specify the type of the `button to prevent the button from behaving unexpectedly (like submitting).
    • Good job on taking care of those icons! 👍
    • Use rem or sometimes em unit instead of px. Using px will not allow the users to control the size of the page based on their needs.
    • Styling
      • The body should have a gray background color. Like @Beats-Ayush has said to you, use background-color property.
      • Give a max-width to the container element to prevent the cards become too wide on mobile layout.
    • Best Practice (Recommended)
      • Write your code with consistent style (e.g. the indentation, quotes, whitespace, etc). If you write your code with consistent style, it will make it easier to read for everyone (including your future self).

    That's it! Happy coding! 😁

    Marked as helpful
  • Abdul•8,560
    @Samadeen
    Posted over 3 years ago

    Hey Shantanu!! Cheers 🥂 on completing this challenge Here are my suggestions 1.You should use <main class="container"> instead of <div class="container">. 2. Go down orderly when you are using the headings h1 down to h2 down to h3 and so on.

    . Regardless you did amazing.. Happy coding

    Marked as helpful
  • Ayush Nath•360
    @Beats-Ayush
    Posted over 3 years ago

    ShantanuBorkar Excellent solution. Some places where you can improve your code-

    • Use the background-color for the body.

    • Use background-color: transparent; in hover-state to pick up the color underlying the button. This way you can avoid applying the individual colors again.

    • Use exactly one <h1> and semantic element landmarks like <main> for better code readability and avoid accessibility errors.

    • Use max-width to restrict the width of the body(Edit: not body but the card component which holds all the contents) to increase responsiveness.

    Marked as helpful
  • ShantanuBorkar•80
    @AlsoShantanuBorkar
    Posted over 3 years ago

    Thank You @Beats-Ayush @vanzasetia @@Samadeen for your advice.

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

Oops! 😬

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

Log in with GitHub