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

Social Media Dashboard with theme switcher using CSS grid and flex-box

Kaung Zin Hein•720
@K4UNG
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


I tried to speed run this but failed miserably. Writing html and setting things up alone took almost an hour. But overall, I'm happy with what I got. I tried using as many semantic tags as I could think of. Any kind of feedback or suggestion on how to improve would be highly appreciated. Happy Coding!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•2,010
    @AlexKMarshall
    Posted over 3 years ago

    This looks great and is nicely responsive. And the theme switcher works well.

    In general, I would suggest that trying to rush things is not a very useful thing to do. Doing things well is far more important, and speed just comes with familiarity.

    In terms of semantics and accessibility, there are a few things to fix.

    The cards have a hover effect and a pointer for the cursor. But there are no interactive elements on them. There is an implication that clicking on this card will do something, but you haven't provided any means to do that (a button or an anchor). So this won't work. And in addition, it won't be accessible for keyboard users. This is an excellent article on how to build proper cards https://inclusive-components.design/cards/

    You have incorrect alt text (e.g. the Facebook icon's alt text says Youtube)

    Be careful with headings. A heading should be meaningful when read independently of other content. And your headings as a whole should read like a table of contents. Currently, you have headers like <h1>1987</h1>. This is meaningless on its own so doesn't work as a good heading.

    Be careful with the level of headings. You should only have one h1 and then every other heading should follow the correct order.

    Careful with what screen readers will read. You've used alt text on the arrow icons. So currently they will read something like "Image Up arrow 12 today". That's better than just "12 today" but it would be better to read something like "Up 12 today". So you can make the icons have an empty alt, and use screen-reader-only text to get the right result.

    Marked as helpful
  • AbdeRaouf Zemmal•680
    @abdraoufx
    Posted over 3 years ago

    Perfect Solution With The Determined Pixels :)

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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