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

Responsive Landing Page with React, Styled Componenets, Grid, Flexbox

Krishna Bansal•20
@Krishna-bansall
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This project was fun, but it took me 2 days to complete am I not up to speed? Does my code use the best practices? Also, I am not sure I Would add background color and image on mobile screens?

Any suggestions will be appreciated, this is my first front-end-mentor challenge 😁

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mark Mitchell•1,820
    @markup-mitchell
    Posted over 3 years ago

    don't worry about speed, that happens naturally with practice.

  • Renaldy Prasetio•70
    @iceofice
    Posted over 3 years ago

    Hi Krishna Bansal,

    Welcome to Frontend Mentor! Well, I am also new here so let's up our skills together! I also finish this challenge in 2 days. I am not really familiar with React but here are my feedbacks,

    1. Add a default value for the timeframe, you can set 1 of them to be active so there won't be any 0 value there, {state === "" ? timeframe["weekly"]["current"] : timeframe[state]["current"]}

    2. Make it responsive! I am not really sure how to do it on React but it will be worth checking out.

    3. Remove any unnecessary console.log() that is used for debugging.

    Great job on finishing this challenge! Keep it up! I really like that animation. It makes me want to learn about animation 😅.

  • sunil-sharma-999•405
    @sunil-sharma-999
    Posted over 3 years ago

    I really liked the hover animation!

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