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

Tailwind Hero Section with Drop Down Menu

tailwind-css, nuxt
Marvin Ranyaole•150
@VaalGeek
A solution to the Intro section with dropdown navigation 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 proud that for the 1st time, I was able to create a drop down menu without calling it from a build it class of any material ui library. I should stop assuming that I fully understand concepts.

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

Z index, I thought I understand how it works, but it was until I had to put it into practice with other components and with other classes that I realized that I don't fully understand.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Koda👹•3,830
    @kodan96
    Posted 12 months ago

    hi there! 👋

    z-index is a tricky property, because sometimes the rendering of the elements depend on the parent container's z-index or position properties. sometimes z-index will not make any difference if you apply it an element with static positioning. if you struggle with z-index, try to apply position: relative; or any other than static (which is the default) positioning to elements. I had a rally hard time figuring this out when I first created a semi-transparent overlay. elements with higher z-index just wouldn't appear above the overlay. then I just applied relative positioning to them and boom.

    the other thing is the isolation property, which also can mix things up, because if you apply isolation: isolate; to the parent element that will create an entirely new stacking context.

    So just check the position attributes of the elements if you get stuck with z-index, and make sure you don't apply isolation to parent elements unnecessarily.

    Hope this helped 🙏

    Good luck and happy coding! 🙌

    Marked as helpful
  • Marvin Ranyaole•150
    @VaalGeek
    Posted 12 months ago

    @koda, but here is another question that has been bothering me, when it comes to the use of Z Index, inside the parent component, the Z index does not work when applied to child components within the parent component (page), you will have to apply it on child components respectively, why is that if you have any clue?

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