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

Project tracking Intro component

Kim•510
@Mismisty
A solution to the Project tracking intro component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I add some problems with the layout, I think its my markup that keeps giving me problems. I would appreciate if someone would take a look at my markup and give me some suggestion, am I using to many div's or not enough maybe I'am not placing them around the content correctly. Thanks for the feedback.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Paras Sharma•700
    @imparassharma
    Posted over 1 year ago

    To be honest your approach of creating divs is not correct....You have to think how will your layout will appear before coding. You should know flex property pretty well so that you can align items easily and in more clean way. You cannot just create divs anywhere and then give them property absolute and then position them using right and left...it is not a good approach.

    Like whats the point of naming a section right side and left side but in reality they are acquiring full page widths.... a more defined approach could have been like container width:100vw....then in html leftPage should be created ...and give it width of 50vw lets say,,and then rightPage with width 50vw.......in container flex direction row so that leftPage and rightPage goes next to each other....align-items center ,...justify-content :center....this is how you will have to proceed....with a particular layout in mind....

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub