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

Responsive news homepage HTML/CSS/JS

P
Kyle Mulqueen•400
@kmulqueen
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?

I'm particularly proud of implementing the responsive navigation - creating a hamburger menu for mobile/tablet that smoothly transitions to a standard navigation bar on desktop. The mobile and tablet layouts came together faster than expected, which felt great after struggling with some of the desktop complexities.

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

The desktop layout gave me the most trouble, specifically with the grid system for the bottom three articles. I spent a lot of time trying to get the images to scale properly with the text content, but there's still an awkward sizing issue between 1280px-1400px screen widths that I haven't fully resolved. The "New" stories section also doesn't scale well beyond 1440px, which is frustrating. Honestly, I reached a point where I needed to step back from the desktop version and move forward rather than get stuck in perfectionism.

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

I'd really like to revisit the desktop layout, particularly making the "New" stories section more fluid across larger screen sizes. The three-article grid at the bottom also needs work to handle the image-to-text proportions better across different breakpoints.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ivan Orsolic•260
    @ivanorsolic95
    Posted about 1 month ago

    You missed the background color of the page, also there are few stuffs that can be done better, regarding to accessibility.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub