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

Responsive Mobile-First social-media-dashboard-with-theme-switcher

Barbara Ward•1,160
@bward67
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?

I love grid so I loved this challenge. In the larger screen-size I set grid-template-columns to repeat(auto-fit, minmax(10rem, 1fr)). This means our grid will create columns as it needs to and as it can fit them and each column will be a minimum of 10rem and it will expand until a new item of 10rem has the room to be added.

First I tried using a checkbox for the toggle and modifying it in CSS but it gave me some problems so I just created a custom toggle.

The part that gave me the most grief and I wasted the most time on - was the linear-gradient on the instagram card. I first tried using border-top with border-color but that didn't work. Then I got it to work using border-image and the linear-gradient but I couldn't get the border-radius to work so I had to change my entire code for this part. Eventually, I created another div and placed it position: absolute in front of the card and put the linear-gradient on the back div and using top and padding-top I madde it work. But I REALLY wanted to make it work using border-image so after this challenge I am going to learn more about linear-gradients and -webkit etc. = because anything is possible - isn't it??

I created two entire dashboards: one for light and one for dark. Then I positioned them absolute and toggled them in JS.

With dynamic data it could be a good challenge especially with the followers numbers and likes etc changing. The arrow up and down and the colors to correspond with them would be fun to do in JS.

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 Barbara Ward'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.