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

homepage news with react and tailwindcss

react, tailwind-css
Sieben•200
@Siebenlist
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I can't stress enough how much fun i had doing this challenge, i don't know what it was but just the approach i had with how to place the items and what could be the best way of doing things really made it so much fun.

As always any feedback is welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted over 2 years ago

    Hi, when using 'flex-direction: column' ensure that the elements are aligned to the left. Also give images a 'width: 100%' instead of pixels to make it responsive, 'max-width' is only for especial cases. Cheers to complete the challenge

    Marked as helpful
  • Maxime•430
    @maxime927
    Posted over 2 years ago

    Hi Sieben, how are you ? I have some tips that i hope would helps you :

    • It seams dificult to use grid with this template as I saw on multiple solutions before, why don't you stay with flexbox ? You'll be able to fix each width and space without being too much constrained with the grid structure.

    • For Designers the result is really important, pay attention to spacings and font-size as well, i can advise you to use the chrome extension : PerfectPixel

    For exemple, for the News block :

    • you can use an <ul> tag to list the elements and almost no responsive style for this block as this below : HTML
    <ul>
        <li>
            <a href="#" title="Hydrogen VS Electric Cars"></a>
            <h3>Hydrogen VS Electric Cars</h3>
            <p>Will hydrogen-fueled xars ever catch up to EVs?</p>
        </li>
        ...
    </ul>
    

    and styles

            ul {
              padding: 0; margin: 0; list-style: none;
    
              li {
                position: relative; padding: 27px 0 12px; border-top: 1px solid $dark-grey; margin-top: 18px;
    
                &:first-child { margin-top: 0; border-top: none; }
    
                a {
                  position: absolute; z-index: 2; left: 0; top: 20px; right: 0; bottom: 0;
    
                  &:hover + h3 { color: $orange; }
                }
                h3 { color: $white; font-weight: 800; font-size: 20px; margin-bottom: 8px; }
                p {color:$grey; margin: 0 0; font-size: 15px; line-height: 26px;}
              }
            }
    

    Hope it helps...

    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
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

Oops! 😬

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

Log in with GitHub