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

TailwindCss&Gulp switcherMode&prefersColorScheme&sessionStorage

Szymon Rojek•4,540
@SzymonRojek
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


Hi everyone! :D,

Finally, I can publish this challenge. I concluded that every project, even small, will teach something. First time I was working with the TailwindCss framework and gulp.

** => Please, let me know if you have got any suggestions, especially about HTML structure and accessibility.**

A short explanation:

  • I have chosen a button but probably the radio-button or checkbox could be a better choice (the design of it could be nicer);
  • I didn't do the border-top gradient because Tailwind doesn't have very good support with it yet (I still learn how to create different plugins);
  • manually switching the mode between light/dark (smooth transition). I want to detect if the user has requested the mode: light or dark (prefers-color-scheme) => in this case I have decided to work with the sessionStorage instead of the localStorage because the main goal was to come back to the user's preferences (prefers-color-scheme) which in the meantime may have changed the theme in the general settings.
  • added small animation updating the total number (the main idea is copied from the web developer but I've changed a bit it's content to get more readable code - in the meantime I want to create my version of it);
  • footer displays on preview site;
  • deploy the project to Github Pages with GitHub Actions.

Thank you so much. Ps. don't forget to upvote my project if you like it.

Greetings :D

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 Szymon Rojek'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.