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

Responsive News Homepage with hamburger menu using Vanilla CSS and JS

accessibility, bem
Archi Halder•90
@archihalder
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone, I would like to share my experience while doing this project.

  • I wanted to try this project as this was on the Wall of Fame.

  • I also tried to make it more accessible and used BEM naming convention.

  • I wasted hours to create a feature, later realizing that there's no scenario where that feature would be useful.

  • I also tried to use background-image instead of img elements for Home page photos, learnt how to change a div size based on the background image, but later found out that this is not good for accessibility. So had to remove it.

  • The hamburger menu was a good challenge. Read multiple articles and watched few YouTube videos. But sometimes it's glitching (not sure why).

  • Overall it was a great project.

  • The Lighthouse scores are 88 in Performance, 92 in Accessibility.

Any feedback about this project would be helpful!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Thomas TS•1,620
    @ttsoares
    Posted almost 2 years ago

    Greetings. Great work ! You did follow the design to the letter :-)

    Just a small issue with the burger menu... Could be my browser, Firefox 116.0.2, though. Anyhow, the behavior I'm referring to is that the menu only do appears if one click the middle bar of the burger icon. If the top or bottom bars are clicked, the menu does not show up !

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