Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 3 years ago

intro-section-with-dropdown

MioMauro•400
@MioMauro
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


I started the challenge not realizing I was unfamiliar with the dropdown menu. Well, 4 days of you tube tutorials + w3schhol while building this project.
On the navbar pop-up/drop-down button, I had never done any. The "easiest" part was the graphics. It's not exactly what the challenge calls for, a little color I think goes a long way. Are we developers or robots? Improvements in progress... Criticism welcome, I'm not offended and I'm not fickle.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pradeep Saini•990
    @pradeeps4ini
    Posted about 3 years ago

    Hey, MioMauro. I hope you had lots of fun and learning while completing the project. I really like how you implemented your own elements in the project.

    I have some suggestions that i think would make the site a little better.

    • Paragraph " Get your team in sync, no matter your location. Streamline processes, create team rituals, and watch productivity soar." is difficult to read because of the background color and the font color. May be change the font color to some other color, which will make the text easier to read.

    • Use flexbox property "align-items:center" to center the nav bar vertically. And also remove the margin-top from it.

    • In the logos section. You don't have to use <divs>. You could use <img> tags only. This way you won't have to align them horizontally. They would be automatically aligned horizontally. <img> are inline elements.

    Some suggestions from another beginner like you. Have fun learning.:)

    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