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

Responsive landing page with react and tailwind

react, tailwind-css, vite
Efobi Francis•360
@Efobi-Francis
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


At first glance, the project looks simple, but implementing the sidebar and dropdown menu and managing the different states respectively was an excellent challenge.

Please check it out and help me with corrections.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • KehindeDaniels•90
    @KehindeDaniels
    Posted over 1 year ago

    I love how you were running away from the image growing smaller @1439px 😂. Mine went too small.

    I've been looking into the issue of the site expanding excessively, and I believe one of the potential solutions is to check and adjust the width and max-width properties of the main container. This should help control the layout and prevent content from overflowing beyond the viewport.

    Personally, I use grid for my general layout, even before I add any content, this way, I can determine the entire space and layout it would take.

    This challenge for instance, my overall layout was

    grid-template-column: 1fr repeat(10, minmax(min-content, 14rem)) min 1fr PS 10px as my root element

    This way, my entire content will never exceed 1400px (and it could be adjusted as needed). The minmax function will give room for individual individual column to expand as needed, but not beyond 14rem (140px)

    The 2 (1frs) are for extra plate 😆, but this way, there are 12 columns, and I have catered for more than 100px without media query

    And for the button in the navigation of the mobile view, if a max-width is applied to it, it will prevent it from expanding excessively

    Thank you

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