Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Time tracking dashboard with typing animation

Kylan Duncan•100
@cloudydaiyz
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'm proud of going a bit above and beyond for this solution. Initially, I was thinking of just completing it regularly, but I want to be able to grow from the projects I create on here, so I decided to add a typing animation. It's not much, but it's setting the precedent for my projects to come.

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

The typing animation whenever a timeframe button was pressed caused the most trouble for this project. Whenever I was first watching tutorials about HTML/CSS/JS, they used the concept of namespaces for declaring elements, and using that concept turned out to be beneficial when selecting the elements for the typing animation.

However, I had a bit of trouble editing the text for the animation, since originally I was editing the innerText property of each element, but the typing cursors for the animation was contained inside each element that I was editing. If I changed the innerText of 1hr|, so that it said "2hrs" instead it resulted in 2hrs and the span getting overridden. I overcame this by recalling the concept of the DOM tree from the tutorials I watched -- I updated the text node (e.g. paragraphElement.childrenNode[0].nodeValue) instead of the innerText.

I'm gonna try to incorporate these concepts more in my future frontend projects, and apply more structure to my code so that I can improve the readability as well.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Kylan Duncan'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 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.