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

FEM | Social Media Dashboard Challenge

accessibility, van-js
Muhammad Zubair•160
@Mini-Elliot
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?

🌟 Social Media Dashboard Challenge - Frontend Mentor

I recently completed the Social Media Dashboard challenge from Frontend Mentor. It was an exciting experience, and I tried my best to make it as accurate as possible.

🚀 Live Preview & Code

🔗 https://social-media-dashboard-kohl-sigma.vercel.app/ 📂 https://github.com/Mini-Elliot/Social-media-dashboard.git


📜 Challenge Overview

The goal of this challenge was to build a social media dashboard with light and dark mode switching. The dashboard displays key statistics from different social media platforms (Facebook, Twitter, Instagram, and YouTube).

🎯 Features Implemented:

✅ Responsive Design – Works smoothly on all screen sizes.
✅ Light/Dark Mode Toggle – Allows users to switch between themes.
✅ CSS Grid & Flexbox – Used for a well-structured layout.
✅ Custom Hover Effects – Interactive elements for better UX.
✅ Accessible & Semantic HTML – Improved readability and usability.


🛠 Tech Stack

  • HTML – Semantic structure.
  • CSS (SCSS) – Modern styling with reusable variables.
  • JavaScript – For theme toggling and interactivity.

🎉 My Experience

This challenge was really fun and engaging! I focused on making the design as close to the original as possible. The most interesting part was implementing theme switching using CSS variables.

💡 Key Takeaways:

  • Learned more about CSS Grid & Flexbox for better layouts.
  • Improved my understanding of CSS variables for theming.
  • Got more comfortable with JavaScript event handling.

👀 Challenges Faced:

  • Tweaking colors for dark mode to match the design.
  • Ensuring consistent spacing and alignment across different devices.

📌 Future Improvements

🔹 Add animations for smoother transitions.
🔹 Improve accessibility for better usability.
🔹 Optimize CSS for cleaner and more maintainable code.


🏆 Final Thoughts

This was a great learning experience, and I had a lot of fun working on it! I’m looking forward to tackling more challenges on Frontend Mentor. 🚀

💬 Feedback is welcome! Let me know your thoughts.

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 Muhammad Zubair'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 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.