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

Social media dashboard using React + Vite + Tailwind

react, vite, tailwind-css
Simon•180
@Simplify4Me2
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'm proud of mastering Tailwind and extending its theme. Tailwind made implementing the dark theme straightforward once the colors were configured. Initially, I created the desktop design, followed by the mobile design. In the future, I'll likely start with the mobile design, as I had to constantly verify changes against the mobile layout whenever I added new elements.

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

I encountered some issues with the toggle component. While searching online for inspiration, I found it challenging to translate traditional CSS into Tailwind CSS.

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

The layout isn't fully responsive as it only supports two sizes: mobile and desktop. The in-between range looks quite off. Any tips would be greatly appreciated.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • haquanq•1,875
    @haquanq
    Posted 12 months ago

    Hello @Simplify4Me2 👋👋

    About responsiveness, the only tips i got for you is adding more breakpoints and slowly shifting the layout (4 col - 3 col - 2-col -1 col for example), a little bit more work but worth it. I notice you are using flex to manipulate each card, use display: grid instead because it supports more grid layout manipulation features.

    About the top colorful decoration pattern, you can use pseudo element ::before / ::after with 'position: absolute' (card with position: relative) to achieve this

    About HTML markups semantic, you are abusing div for everything. Consider other HTML elements like section, article, ul, li, p, small, strong,... . For example each section of card could be using ul, li to represent a list of cards (with the same context).

    Hope this help, happy coding 🔥🎇🎇

    Marked as helpful

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub