Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 27 days ago

HTML, CSS, JS, Git, GitHub, Netlify, PerfectPixel, Lighthouse

accessibility, bem, lighthouse
Elmar Chavez•580
@CodingWithJiro
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


What are you most proud of, and what would you do differently next time?

Yesterday I learned to implement a theme-toggle for my site's dark and light theme.

I applied it for the first time in this project and will be applied on my future projects from now on.

What challenges did you encounter, and how did you overcome them?

The implementation of a theme-toggle button is a bit hard but I managed to pull it off by reading some resources and by trial-and-error

What specific areas of your project would you like help with?

What to do if the style guide doesn't seem to match the design image given?

  • I don't know if my eyes are lying to me but it seems like font-weight: 700 is not the right value for the Big Shoulders font for this challenge

  • I downloaded the font-weight: 500 version and implemented it instead

  • Even though I kinda made my final solution as close as possible to the design intended, I still doubt myself if I made the right decision

  • I feel like 700 was the right font-weight all along and I'm just missing a simple CSS property to make it work (I tried letter-spacing but did not come close)

I hope someone can take quick inspection of my CSS code. Thank you in advance!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • haquanq•1,995
    @haquanq
    Posted 27 days ago

    Hi @CodingWithJiro,

    I think the heading supposed to be bold (700), but the font seems to have small different between 500 and 700 which lead to confusion.

    I took a look at your CSS and i think your variable names seem kind of aggressive to me 😆.

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

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