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

Responsive landing page using CSS Grid and JS

lsh•160
@SH-Lee2
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I feel this project was a bit difficult. Please any feedback on how to improve is welcome. :) 😊

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, great work on this one. Layout is great on desktop, it is responsive and the mobile layout looks great as well.

    Fidel Lim already gave some great tips on this one, just going to add some suggestions as well:

    • Person's img should be using the person's name as the alt. In component like this when a person's image and name are both present, always make use of their name as alt.
    • Also I saw some usage of id as a selector, don't use this since it is a bad practice due to high css specificity, leave it to class for selecting elements.
    • li alone is not accessible for the selections. An interactive component needs to have interactive elements. On this one, you could either use button inside the li element, just make sure to add an aria-live element that announces a certain option is selected, since button alone is not informative enough. Another method is to use radio buttons in here, since it is a selection of only one choice right and radio buttons are great for those. It will be inside a fieldset along with a screen-reader only legend defining what is the purpose of the sets of radio buttons. This is much informative.
    • Those 6 cards could be sitting in a one whole grid instead of making 2 containers to wrap the top part and other one for the bottom part.
    • You could use a heading tag for each title of the card since they give overview on what the section is all about also you don't need to use header to wrap it, a div would be fine.
    • Decorative image must be hidden at all times by using alt="" and extra aria-hidden="true" attribute on the img tag, so hide the 3 dots.

    Aside from those, really great work on this.

    Marked as helpful
  • Fidel Lim•2,775
    @fidellim
    Posted almost 4 years ago

    Hi!

    Well done finishing the project! Looks great for both desktop and mobile views. Just one suggestion I would like to share is that you could add some margin to the component so that it has some space between the screen border and the component itself. Other than that, I think everything seems done well :) Hope it helps.

    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

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