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

flex box , css variables , normalize

accessibility
Erik Emmanuel Navarrete Reyes•400
@apuntesnavarrete
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'd like receive feedback

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Travolgi 🍕•31,300
    @denielden
    Posted about 3 years ago

    Hi Erik, great work on this challenge! 😉

    Here are a few tips for improve your code:

    • Tip of graphic design: with font-family:" Big Shoulders Display ", cursive the browser will use the Comics Sans font when it doesn't find the first font indicated (you can seen during loading)... for the designer it's a really awful font! I would rather replace it with a font-family:" Big Shoulders Display ", sans-serif much more similar to the primary font.
    • add transition on the element with hover effect
    • instead of using px use relative units of measurement like rem -> read here

    Overall you did well 😁 Hope this help!

    Marked as helpful
  • Louise Willoughby•80
    @Louise-Ann93
    Posted about 3 years ago

    Hey Erik 🙂 I thought your solution was really good. I love how they snap on breakpoint and all the style is still even! I only had two points really,

    • I'm not sure if you can change the break point to snap at a larger screen point just because the cards started to hide behind the screen while i was adjusting the size before the cards snapped alignment (unless thats the spec breakpoint i haven't checked).
    • The button style i see you had for active, these didn't seem to do anything? I can see you tried to have the button colour change but that didn't happen for me.
    • The buttons say 'Click Me!' rather than 'Learn More'

    Those are only minor points though otherwise it looks good 🙂

    Marked as helpful
  • Shashree Samuel•8,860
    @shashreesamuel
    Posted about 3 years ago

    Excellent work Erik

    Keep up the great work

    I have some feedback regarding the design aspect of your solution

    • The title in each card has the incorrect font family from the one specified in the style-guide.md file likewise the button in each card.

    • The title needs to be uppercased using the css property text-transform: uppercase.

    In terms of your accessibility issue

    • All page content should be contained by landmarks, this is caused by the non-identification of a semantic html tag which can be fixed by wrapping all the elements between the body element within main tags.

    Read more on semantic tags here

    I hope this helps

    Cheers

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