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

Mobile first Time Tracking Dashboard

Veronica Orozco•260
@VLOrozco
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey frontend community!

Here is my solution for the time tracking dashboard. It functions, however, I manually wrote my JavaScript and know there has to be a way to condense the amount of lines I wrote.

Here are my q's:

  1. How can I simplify my JS code and still have the same functionality?

  2. I've noticed a pattern on my accessibility report. Suggestions are appreciated or a link to the best resource for practicing/learning more how to fix these issues.

Thanks for your time and happy coding! ~V

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Enmanuel Otero Montano•2,155
    @Enmanuel-Otero-Montano
    Posted almost 3 years ago

    Hola Veronica!

    En este desafío te proveen un archivo JSON para cargar los datos desde ahí, no es obligatorio usarlo, pero te recomiendo que los uses, pues es como se trabaja en proyectos reales. Imagínate que tengas muchos más datos, tu HTML sería inmenso. Te recomiendo que cargues los datos del archivo JSON desde el JavaScript. Tal vez esto va a ser un poco más desafiante, pero será mucho mejor, eso se hace con la API Fetch (te dejo enlace).

    Después que estés cargando los datos desde el JSON puedes escoger cualquier período de tiempo para mostrar sus respectivos datos cuando se carga la página y agregar eventos de escucha para cada botón (Daily, Weekly, Monthly) y según donde se haga clic tu cargas los datos. Si haces esto vas a tener menos código HTML y menos JavaScript. Te dejo enlace a un video donde lo explican muy bien.

    Video sobre Fetch

    Te dejo un enlace al repositorio de mi solución por si quieres mirar para tener una idea.

    Repositorio de mi solución

    Cualquier duda puedes preguntar.

    Saludos!

    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