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

News homepage (React and Tailwind)

react, tailwind-css
mehdias63•330
@mehdias63
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

  • Ehsan Tatasadi•1,800
    @tatasadi
    Posted over 1 year ago

    Very good job on completing this Frontend Mentor challenge! Your project looks very promising, and the structure you've implemented using React components is well thought out. Here are a few small suggestions to further refine your work:

    Logo and Navbar Alignment

    From medium (md) screen sizes and up, ensure the logo is vertically aligned with the navbar items. This might require adjusting the flexbox properties or margins/padding specifically for these sizes to achieve a visually balanced layout.

    Grid Layout Adjustment

    While the main grid setup works well for mobile view, consider moving your grid layout inside the main tag for desktop views to avoid stretching content unnecessarily due to min-h-screen. This change could help manage the extra spaces more effectively and ensure content is distributed as intended across different screen sizes.

    Single H1 Usage

    Ensure there's only one <h1> element used on the whole page to maintain semantic HTML practices and improve SEO. The <h1> tag should represent the main topic of your page. For other headings, use <h2>, <h3>, etc., to indicate subheadings and maintain a hierarchical structure.

    Implementing these suggestions will not only enhance the aesthetics and alignment of your project but also improve its semantic structure and accessibility. Keep up the great work!

    Marked as helpful

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