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

Responsive intro component with collapsible navbar

Syed Ali Mansoor•460
@syedalimansoor
A solution to the Project tracking intro component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello! 👋

Another great challenge! However, I did not find this one to be as intriguing as the others I've done—perhaps I prefer developing singular components instead of full pages 😬

But I'm determined to do more, if only to overcome this prejudice 🤣

Most of the stuff in this challenge was something I have now gotten used to, but the collapsible navbar was slightly tricky. I was able to successfully make it, however! 😁

Please do go through my solution and leave some feedback!

I was thinking of completing some challenges with React (something I've never done yet) so that I could learn and practice it, can you guys link a few challenges which may require 'the React mindset'? Would really appreciate it!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted about 4 years ago

    Hi, Syed Ali Mansoor! 👋

    Nice to see you complete another challenge! 😀 I'm still really liking that attribution every time I see it and I think you've done a good job on the rest of this challenge! 🙌 And, haha, sometimes working on small components is just nice because it's easier to think about and work on everything! 😅

    You should definitely give React a shot because that will allow you to separate your apps into smaller components that you can isolate and think about them on their own. 👍 I think most challenges here would work well with React but a few suggestions (off the top of my head) might be the Bookmark landing page (since it has a few reusable components and some JS stuff to have fun with) or the Jobs listings with filtering (for the same reasons, mostly). 😉

    Keep coding (and happy coding, too)! 😁

  • P
    Patrick•14,265
    @palgramming
    Posted about 4 years ago

    Everything looks really good but you might want to check the text "to see a preview" on the bottom of the page and how it is wrapping in the mobile view but everything else looks really good. Nice Job!!!

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 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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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