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

Social Dashboard ( Vanilla JS Dark theme )

Mustafa•415
@Mostafa-T
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


Hey👋 ,

I was really happy working on such a project and I would definitely be happier if you told me your feedback honestly, So I can Improve my skills 🖥.

Thanks!!✌🏽👨🏽‍💻

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Szymon Rojek•4,540
    @SzymonRojek
    Posted over 4 years ago

    Hi Mustafa,

    Good job!

    A few tips from me:

    • remove comments from the head, people should know what the content is about;
    • in your code are many divs. Divs are semantically inert elements — elements that don’t really do or say anything. The term "semantic" refers to the meaning of a word or a thing, so "semantic elements" are elements designed to mark up the structure of a document in a more meaningful way, a way that makes it clear what they're for, what purpose they serve in the document. Please, check the MDN documentation. Therefore, it will be amazing to use semantics tags like main, section, article, header etc.
    • also, a few times you have used the span tag. IMO SPAN (and DIV) elements by themselves are generally considered to be semantically neutral. A good approach is to use semantic markup as much as appropriately possible, so instead of it you can use paragraphs, ul/li but of course, it all depends on the context. Sometimes I use the span but before it, I try to think about the other semantic tags;
    • accessibility: there is no any important attributes for icons, links, toggles like an aria, role etc. This is a huge topic but very valuable and it is important to read about.

    CSS:

    • it is good practice to reset the styles at the beginning of your CSS file, for example:
    * {
      margin: 0;
      padding: 0;
      box-sizing: border-box;
    }
    

    Design

    • check your main heading h1, on mobile size, it is too big. You can make it more responsive to different devices;
    • the line after "total followers" could have more opacity so it will be more "smooth", at the moment it looks like a LINE that strongly divides the space between headings and sections below;
    • icon arrow up and down should be close to the centre of the text (it will look nicer);
    • you did not consider other devices in your breakpoints: there is a big gap between mobile and desktop. RWD on mobile seems to work well but try to include the tablets etc. What do you think about it?
    • you can add hover to the cards when is a dark mode and smooth transitio;

    That's it from me. Ps. don't forget to upvote any comments on here that you find helpful.

    Many greetings :D

  • Szymon Rojek•4,540
    @SzymonRojek
    Posted over 4 years ago

    @Mostafa-T

    I have forgotten to mention that you can fix the accessibility issues in your HTML report. Accessibility - in this instance, I can recommend an article from the Smashing Magazine: Building Inclusive Toggle Buttons. Let me know what do you think about this article.

    Have a good reading :D

  • Mustafa•415
    @Mostafa-T
    Posted over 4 years ago

    Thank you so much!! Really I can't be more grateful and for sure will improve this project. ❤️❤️

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