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

Frontend Mentor - Time tracking dashboard solution

fetch, accessibility
imad•3,330
@imadvv
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Greetings Frontend Mentor Community!!

This was a great challenge for more practice, I get more practice using Grid and flex, but learned new things as well.

maybe the most interesting one, was the New syntax for range media queries, @media (400px <= width <= 600px ).

but over, Any feedback will be awesome

Happy Codding!!, and have a Good Day/Night

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Edis•1,220
    @edo979
    Posted almost 3 years ago

    Hello. Great work. I read your javascript file and add some changes. You javascript is excellent do not worry. I did this because I was bored and love javascript.

    let data = [],
    selectedTimeFrame = 'daily'
    
    const buttons = Array.from(document.querySelectorAll('[data-show]'))
    const currentElements = Array.from(document.querySelectorAll('.current-data'))
    const previousElements = Array.from(document.querySelectorAll('.previous-data'))
    
    fetch('../data.json')
      .then((res) => res.json())
      .then((result) => {
        data = result
    
        updateView()
      })
    
    // Event listeners
    buttons.forEach((button) => {
      button.addEventListener('click', (e) => {
        selectedTimeFrame = e.target.dataset.show
    
        updateView()
      })
    })
    
    function updateView() {
      data.forEach((activity, i) => {
        const currentValue = activity.timeframes[selectedTimeFrame].current
    
        currentElements[i].textContent = currentValue + getTimeUnits(currentValue)
    
        previousElements[i].textContent = formatTextPrevEl(
          activity.timeframes[selectedTimeFrame].previous
        )
      })
    }
    
    // Utility
    function getTimeUnits(value) {
      return value > 1 ? 'hrs' : 'hr'
    }
    
    function formatTextPrevEl(number) {
      const timeUnit = getTimeUnits(number)
    
      switch (selectedTimeFrame) {
        case 'daily':
          return `${number}${timeUnit} - yesterday`
    
        case 'weekly':
          return `last week - ${number}${timeUnit}`
    
        case 'monthly':
          return `last month - ${number}${timeUnit}`
    
        default:
          return
      }
    }
    
    Marked as helpful
  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hey Imad, great job here, and thanks for sharing that info about the range for media query, which I did not know about! How do you like working with it, and how does that make you write your CSS differently from what you normally do for media queries?

    I love the tablet view that you have, and I wish I thought of that when I was building mine; I might try changing to this view you have later when I make some tweaks.

    I think the only comment I have is, I notice in your JS and the display that you have "last day" as the label for the previous stat from yesterday; in English it's probably more correct to use "yesterday", since "last day" has more of the meaning of the last day in a period, like the last day of the week, or last day of the month, and we don't normally think of last day as the previous day (as in yesterday).

    That's all really, great work once again!

    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

Oops! 😬

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

Log in with GitHub