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

News homepage - HTML5 , SCSS, Vanilla JS, Mobile First.

Fernando Batista•630
@FernJBatista
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Habeeb Kareem•740
    @olaide-hok
    Posted 4 months ago

    Great work!

    Some areas to improve on are:

    • there is an overflow on mobile view.

    • CSS Reset: the reset is overly verbose and includes many elements that may not be necessary. Consider using a more concise reset like Normalize.css or Modern CSS Reset. Alternatively, use a tool like PostCSS to automate resetting only the elements you use. I personally use Normalize.css.

    • Repetitive Media Queries: the media queries are repeated for similar breakpoints (e.g. $tablet-breakpoint, $desktop-breakpoint). This can be streamlined using mixins or utility classes. You could create a mixin for common breakpoints for example

    @mixin for-tablet {
        @media screen and (min-width: $tablet-breakpoint) {
            @content;
        }
    }
    
    @mixin for-desktop {
        @media screen and (min-width: $desktop-breakpoint) {
            @content;
        }
    }
    
    @mixin for-big-screen {
        @media screen and (min-width: $big-screen-breakpoint) {
            @content;
        }
    }
    

    and you could use like

    header {
        padding: 2rem 1rem 1rem;
        max-width: $tablet-breakpoint;
    
        @include for-tablet {
            max-width: $desktop-breakpoint;
        }
    
        @include for-desktop {
            max-width: $big-screen-breakpoint;
            padding: 2rem 2rem;
        }
    }
    
    • Lack of Utility Classes: there are repeated styles (e.g., display: flex, gap: 1rem) could be abstracted into utility classes for reusability. You could create utility classes such as:
    .flex {
        display: flex;
    }
    
    .flex-col {
        flex-direction: column;
    }
    
    .gap-1 {
        gap: 1rem;
    }
    
    .gap-2 {
        gap: 2rem;
    }
    

    and usage would be:

    #newsContainer {
        @extend .flex, .flex-col, .gap-1;
    }
    
    • the font-size for the h1 max-value is 56px, the clamp values can be updated.

    • the spacings as well could be updated for large screens.

    Overall, great work, well done.

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