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

News-Homepage using CSS Grid and Vanilla Javascript

Eric Aguayo•1,055
@EAguayodev
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

What I Am Most Proud Of One of the aspects I am most proud of in this project is how resourceful I became when tackling CSS Grid. Despite the initial challenges, I diligently utilized the CSS documentation. This approach helped me overcome the complexities of CSS Grid, greatly enhanced my problem-solving skills, and deepened my understanding of responsive design principles. My ability to adapt and learn on the go was pivotal in successfully achieving the optimal layout for various device screen sizes.

Plans for Improvement Next Time: Looking ahead to future projects, I'd like to implement several improvements to refine my development process and enhance the quality of my work. One specific area I plan to focus on is the structure and semantics of my HTML. For instance, I intend to incorporate .

What challenges did you encounter, and how did you overcome them?

Challenge with Open and Close Functionality in JavaScript:

One of the significant challenges I encountered during this project was implementing the open and close functionality of the mobile navigation menu using JavaScript. The primary issue was ensuring that the menu behaved correctly across different devices and user interactions, such as tapping outside the menu to close it or interacting with menu items. To address this challenge, I adopted a straightforward yet effective approach:

Mobile Open and Close Variables: I defined specific variables in JavaScript to represent the state of the mobile navigation menu ). These variables helped track whether the menu was currently open or closed. Event Listeners: I added event listeners to the menu button for 'click' events. These listeners triggered functions to toggle the isOpen state, effectively showing or hiding the menu as needed.

Simple if/else Logic: I used simple if/else statements to manage the menu's visibility within the functions triggered by the event listeners. If the menu was open (isOpen is true), the script would close it, and vice versa. This logic ensured that the menu responded intuitively to user interactions.

CSS Transitions for Smoothness: I utilized CSS transitions to smooth out the open/close actions. This not only enhanced the user experience by providing a seamless visual transition but also aligned with the website's responsive nature.

What specific areas of your project would you like help with?

I would like feedback and help with specific areas, such as whether the CSS transitions for smoothness work on the user end.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Eric Aguayo's solution.

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.