Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Intro Section with dropdown | JS, BEM, Transition

bem
Chee Kian Teoh•330
@teoh4770
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


Feel free to leave feedback and help me improve my code structure or even the solution!

Hi there! This is my attempt at the Intro Section with Dropdown. It has been almost 2 weeks since my last attempt on a challenge. These days I have been started to learn about Angular. While learning new stuff and coding along is fun, it gets bored really fast. Therefore, I decide to do a FM challenge since there is no loss.

I have ...again, almost forgotten most of my fundamental, especially the way to structure my CSS and JavaScript code. But referring to my previous work really help me get back to my feet and complete this challenge with 100% satisfaction :D

Lesson I learnt:

  1. Refer back my own previous code, or other's code is a good way to learn/refresh
  2. Always plan the code structure out before writing the code

This is what I practicing:

  1. BEM naming convention
  2. Transition (using position, transform and opacity property)
  3. JS: Controlled the DOM by toggling the classes

Extra:

  1. Adding little touch on the design by referring to other people's works
  2. Switching the plain images to animated GIF from Flaticon

Happy Coding everyone :D

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Todaymore•460
    @Todaymore
    Posted almost 2 years ago

    Really great work Bro! There is a lot to learn from you, I am a Junior Programmer, and I can create fair website design but I am stuck at responsive designing. If you have time then please visit my solution and advice me about how to improve my Responsive Design for media sizes.

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