Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

Social Media Dashboard with Theme Switcher 📈 [HTML, SCSS, JS]

sass/scss, vite
Tharun Raj•1,330
@Code-Beaker
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


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

A really fun project built with SCSS!

Thanks to SCSS which made the theme switching much easier than regular CSS. I was able to achieve the result with a few lines of SCSS. This project is built using Vite to make working with SCSS easier.

This project also uses some basic grid layouts as well as some complex flex layouts that look amazing together. Building it was really fun because of this. This time though, I wasted lots of time by manually typing and not copy-pasting the contents of the index.html file provided with the Starter files. But, that didn't make a huge difference in terms of time.

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

Currently it doesn't have the toggle button. I'm currently learning how to make it. So as a placeholder, I added a simple button which lets the users toggle the theme. As soon as I'm comfortable building the theme switcher in a better way, I will make sure to update this solution.

One challenge was choosing the right colour each components. This project has a massive colour palette and probably the biggest I've ever worked with. Choosing the appropriate colours for each theme and active states took a little bit of thinking and time. But, that wasn't really an issue.

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

I would like to know how it looks on different screens and how I can make my SCSS, HTML and JavaScript better. I feel like I still have a long way to go with SCSS as my code doesn't look that pretty.

Any feedback is welcome! 😄

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Tharun Raj's solution.

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.