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

3 column preview card using HTML and CSS

Marcus Hugo•365
@marcus-hugo
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 well did I use the CSS display and position properties?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted almost 4 years ago

    Hi there, Marcus! 👋

    Congratulations on completing your first Frontend Mentor challenge! 🎉 Nice job on this one! 👏

    One or two things I suggest are,

    • Switching to a mobile-friendly layout sooner to prevent a horizontal scroll bar from appearing along the bottom of the page when the width of the screen decreases in the desktop layout. It's important to make your solution look good on all screen sizes so that as many people as possible can view and enjoy your work.
    • Adding the light-grayish background color from the original design to the page.
    • Perhaps using anchor tags (rather than <button> elements) for the "Learn More" elements in the card (since they seem like they will take the user somewhere when clicked). 😉

    Also, +1 to what Vanza suggested about considering using flexbox and CSS grid in your CSS—they certainly make laying out things a whole lot easier! 😅

    Keep coding (and happy coding, too)! 😁

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 4 years ago

    👋Hi Marcus! My name is Vanza!

    In my opinion, the way you use CSS display and position properties aren't in the right circumstances.

    Even though, it is working, but keep repeating yourself is not efficient, like keep adding width and height properties (because it is set to position: absolute) on .*-card.

    For this challenge, try to use CSS Grid and CSS Flexbox, to complete this challenge again or another challenge using those technologies. It will make your CSS much cleaner and simple.

    That's it! Happy Coding!

    Marked as helpful
  • Marcus Hugo•365
    @marcus-hugo
    Posted almost 4 years ago

    Thanks for the suggestions!

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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