Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Dashboard with Light/Dark Theme Switcher

accessibility, bem, lighthouse, sass/scss, tailwind-css
P
Daniel 🛸•44,740
@danielmrz-dev
A solution to the Social media dashboard with theme switcher challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


🛸 Hello Front-End Mentor Community! I'm Daniel and this is my solution for this challenge! 😊

🛠️ Built with:

  • HTML
  • SASS
  • Tailwind
  • JavaScript
  • BEM Notation
  • Mobile First workflow approach

Another very fun and challenging project. That Instagram container with the gradient border gave me a hard time 😅

Now I know how the Light/Dark Modes are made.

If you have any suggestions on how I can improve this project, feel free to leave me a comment!

Feedback welcome 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alexandar Živkovič•70
    @stashix
    Posted over 1 year ago

    Love the translateY for the split background, I should have thought of that :)

    Were you going off of the Figma or just that good of an eye for detail? The positioning is near perfect.

    I think the Dark Mode toggle could be improved by respecting the prefers-color-scheme media query by default and only overriding the browser preference on toggle.

    Plus if toggled the state could be persisted in local storage.

    Marked as helpful
  • Ahmad Maartmesrini•120
    @Ahmad-Maartmesrini
    Posted over 1 year ago

    I love how you used a span for the toggle, made it much easier to click. I used buttons now the user has to click on the other button to switch the toggle.

  • Account deletedPosted over 1 year ago

    Hello Daniel, I'd like to share some thoughts on enhancing the responsiveness of our website. Specifically, when the screen width is less than 1025px, the current layout displays just one card. To optimize the user experience on mobile and tablet devices, let's consider adjusting it to showcase three cards or more. Implementing a flex-wrap property will facilitate this change seamlessly. Looking forward to your insights and collaboration on making these adjustments for an improved mobile and tablet responsiveness.

  • chems eddine bourabia•150
    @chemsodev
    Posted over 1 year ago

    perfection❤

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

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