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

Time tracking Dashboard with vannila js and CSS

Marko Djurdjevic•330
@Frozennn
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 happy with the way I structured the code, I think it's clean and easy to understand

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

I have a problem I would like help with,

If you select any article except the biggest one, and remove box-shadow property for it you might notice at the bottom edges of the article there is like 1 px of article background color that is showing and it looks bugged. I was wondering why that occurs and is there any quick fix for that? I made it not look so obvious by applying box-shadow but I was hoping someone could explain to me why this occurs and what would be best fix for it. It feels like border radius isn't clipping properly and hence leaving that annoying 1px of background color

Another thing that came to my attention when I was working on this is when I added 15rem padding on the body and I noticed on certain screen widths for example : 1200px-1235px and again from 1080px - 1112px is that divs with class 'article-text-container' got condensed and didn't stretch till the end of the article(card) and made a weird looking appearence because the article background color covered the remaining empty space instead of those divs. Why does that happen? I would really like to know and what would be the best way to fix it besides the obvious one which is removing the padding from the body like I did. Because I might find myself in similar situation where I won't maybe be able to remove the padding.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

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