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

Todo app with React.js and styled components

pawel975•190
@pawel975
A solution to the Todo app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had a problem with setting responsive background image, when changing from mobile to desktop, because I have two seperate images for each version. I used display in media query to manage this but I wonder how I could do this the other way. I would be grateful to get some feedback on this issue or any other feedback too.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roc Tanweer•2,500
    @RocTanweer
    Posted about 4 years ago

    Hello 👋 @Pawel

    Really nice attempt 👍 for this challenge

    I like the transition you have on theme toggler..!

    Suggestions 😃 :

    1. You should always put aria-label to inputs in case they don't have a label for accessibility issue. And there shouldn't be a form without submit button.
    2. Add local storage so save bothe the theme and also the user activity.
    3. Add outlines to every button, input field and custom checkbox for key board user.

    Now your main request 🙂...

    1. What I did, I set that image as background of the header for desktop and mobile as usual. Now I made a class called light and did same thing for light theme. Now I am toggling this class 'theme' and what it does, it overrides the default background-image of header for both desktop and mobile.

    Hope it helps(happy coding..! )

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