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

Responsive grid with hover and dynamically loading data

pure-css, vanilla-extract
Sam•170
@wotanut
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 so proud of the layout, it took me several hours to perfect but I think it looks really good.

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

My biggest challenge was getting the rounded of the cards. I couldn't understand how to get it so that the bottom of the card appeared rounded underneath the top of it, I found out I had to use the background colour of the top of the card and then set another background colour for the bottom of the card whilst rounding it out.

Some other challenges I faced included trying to get the javascript to work on my server (it worked fine in localhost) but I think this was a chacing issue as it worked fine through private browsing. Another challenge I faced was with the icons and overflow:hidden not actually hiding the content.

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

I'd like help with my styling, i'm sure there was a faster way to write my stylesheets (or a better) Perhaps I could've used container queries? Is this a good way to go?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•9,350
    @MarziaJalili
    Posted 6 months ago

    Nice work!

    Here's a more concise way for the card:

    • First, you can use the <section> element instead of the <article>.

    The <article> element is used when its content is fully independent, but here the card is somehow related to other parts of the page.

    • Second, you don't need to set a whole separate <div> for the top border of the card.

    • Take the code below as an example for html:

    <section>
      <div class="card-content">
        <div class="head">
          <span>study</span>
          <img src="./images/icon-clock.svg" alt="dots">
        </div>
    
        <Strong>2hr</Strong>
        <span>Yesterday - 2hrs</span>
      </div>
    </section>
    
    • Then, you can simply apply the code below for styling it:
    section {
      background-color: orange; 
      /* the orange background will be only shown for the border
      /* use these line to set the border */
      padding-top: 2rem; 
      background-image: url("./images/icon-view.svg");
      background-repeat: no-repeat;
      background-position: top right 10%;
    }
    
    .card-content {
      background-color: gray;
      display: grid;
      gap: .5rem;
    }
    
    .head {
      display: flex;
      justify-content: space-between;
    }
    

    You can change the border's color and the image's url for each card by having separate class names or using the :nth-child() selector.

    The web looks cool overall, you're doing great!

    😎😎😎

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