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

Solution Project tracking intro component

tailwind-css
Stefan Bojkovski•720
@xStephx
A solution to the Project tracking intro component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abhi•490
    @abhi-zero
    Posted 8 months ago

    In the mobile version of your site, the image overflows to the right side. To fix this, I think you should use md:hidden { overflow: hidden;} </code> because there is a div with the class name md:hidden, and you placed the image inside it. We need to apply the overflow rule to the container, which is why it should be written like this.

    Marked as helpful
  • Flávio César•340
    @flaviocmb
    Posted 8 months ago

    Well done!

    I think this would solve the overflowing

    html {
      overflow: hidden;
    }
    
    Marked as helpful
  • Yacoub AlDweik•3,090
    @YacoubDweik
    Posted 8 months ago

    Well done Stefan and thank you for your progressive support!

  • ArthurAraujo209•40
    @ArthurAraujo209
    Posted 8 months ago

    🔥

  • SATISH•150
    @satish064
    Posted 8 months ago

    What JavaScript does in this project? And Amazing UI I love it.

  • MarkPraise•150
    @MarkPraise
    Posted 8 months ago

    Nice, But consider Giving the main Container a max width for the desktop

  • Darshan-choubisa•130
    @Darshan-choubisa
    Posted 8 months ago

    hello your design is really nice !! If you don't mind Can you please accepet my friend request on DIscord
    if you can then here is the link : https://discord.gg/uenjjt2a OR @FRIDAY please!!

  • Lordgebrio•190
    @Lordgebrio
    Posted 8 months ago

    Genial la web se ve muy bien.

  • Mudasir Nadeem•430
    @mudasirNadeem
    Posted 8 months ago

    greate

  • Alvaro Prado Tenorio•200
    @frontsitoz
    Posted 8 months ago

    Está muy bien tu solución, felicidades 🙌🏾!! Incluye HTML semántico, el código bien estructurado y legible, y cumples con todo . Sigue así 🫡

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

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

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

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

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

Oops! 😬

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

Log in with GitHub