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

Time Tracking Dashboard

react, typescript, vite, sass/scss
aurobyte•130
@taranjeetsingh9
A solution to the Time tracking dashboard 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 am proud of logic building part as well as my new learning about typescript, vite working with scss it's great.

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

Face significant challenges in use state understanding but time investing in undestanding them worth.

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

I have doubt regarding the setting up css for project as we have #root div inside index.html then we set up other div styling and it mix up styles and layout. So if someone suggest me great resource son how to style react components and index.html so that in starting we have good layout.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Huy Phan•3,430
    @huyphan2210
    Posted 7 months ago

    Hi, @taranjeetsingh9,

    I checked out your solution and wanted to share some feedback:

    You can organize your SCSS files similarly to how you structure your components. In React, it's common practice for each component to have its own .tsx and .scss files, grouped within a folder named after the component. For example:

    └── components  
        └── Button  
            ├── Button.tsx  
            └── Button.scss  
        └── Header  
            ├── Header.tsx  
            └── Header.scss  
    

    You can then import the component’s SCSS file directly into its .tsx file, similar to how you import main.css in main.tsx.

    Keep in mind that component styles aren’t scoped by default in React. This means that class and ID selectors can affect the entire page. To avoid unintended styling conflicts, be intentional with how you name classes and IDs.

    Hope this helps!

    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

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