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

Four card feature section ๐ŸŒœ Dark-mode / Light-mode feature

Yazdunโ€ข1,310
@Yazdun
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello my fellow developers ! Here is my solution for this challenge with a extra feature :

  • I used grid to position cards.
  • I added dark and light mode as a extra feature.

And I have some questions :

  • It's first time I'm adding dark-mode to my project and I was very unfamiliar and had to do a lot of research, What are best practices to create dark mode using sass ? Is my approach any good ?

  • This should've loaded initial theme based on user's OS theme, But it seems like It's not working after deployment, does it work for you?

  • Can you switch themes or is my solution broken ? ๐Ÿ˜

โœ… Let me know your thoughts and feedbacks on this

Code
Couldnโ€™t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Kenโ€ข4,915
    @kens-visuals
    Posted over 3 years ago

    Hey @Yazdun ๐Ÿ‘‹๐Ÿป

    I've got some feedback for the project.

    • For the icons, add aria-hidden="trueโ€, because they are for decoration. You can read more about aria-hidden here. For example:
    <img class="card__icon" src="./images/icon-team-builder.svg" alt="" aria-hidden="trueโ€>
    
    • Next, <div class="header"></div> should be <header class="header"></header>

    Now what comes to the questions:

    • I'm not really experienced with dark mode and how to implement it, so I'll let other mentors to give some suggestions on that.
    • When I first opened the website, I was going to tell you to add a feature to load the site based on user's preferences, but then I saw the question. Unfortunately, that option is not working, it just opened in white mode, whereas my theme of preference is dark.
    • Overall, you added a cool feature, and it works as expected.

    I hope this was helpful ๐Ÿ‘จ๐Ÿปโ€๐Ÿ’ป Cheers ๐Ÿ‘พ

    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