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

My first responsive 3 column preview card challenge with HTML and CSS

Immanuel Tenga Ntjamba•40
@ImmanuelTenga95
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


Above is my solution for the 3 column preview card challenge using HTML and CSS only. I learned a lot in this challenge.

I would like to receive feedback on my approach and solution. Thanks

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shahin NJ•1,190
    @SJ-Nosrat
    Posted almost 4 years ago

    Hi Immanuel, Wonderful solution! The only things I'd suggest is the following:

    1. Please create a separate file for your CSS stylesheet and link your HTML file to your stylesheet by adding <link rel="stylesheet" href="./css/main.css"> in your <head> in your HTML. Note that href="./css/main.css" is the relative path to your CSS file (it might be located in a different folder on your computer).

    2. Start using semantic HTML, here is the MDN article on semantic HTML. Using <div>'s is considered bad practice; specially considering accessibility issues when it comes to screen readers. For example, change the code: <div class="attribution"> to <footer class="attribution"> as the footer describes to you and screenreaders that this is the footer content, instead of a generic <div> element.

    3. Add some margin on your .container class when viewing on mobile screens as this will create some whitespace and give a nicer user experience.

    4. Lastly, I noticed that you built your solution starting from the desktop design then scaling down to mobile. Rather start your solution from Mobile design to Desktop design; as again this is best practice, and avoids a lot of headaches.

    Here is a YouTube video by Kevin Powell describing the Mobile first principle/approach to coding up websites.

    Hope the above helps!

    Best of luck on your coding journey!

    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 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.

Oops! 😬

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

Log in with GitHub