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

NextJs - Tailwind CSS - Shadcn UI

next, tailwind-css, shadcn
Grecco Oliva, Franco•290
@GreccoOliva-Franco
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've built the Mobile UI first with "flex flex-col" and, when tackling the Desktop UI, I had to fully change it to grid. It was fast and easy (very important)

Future improvements:

  • Design the layout taking into acount both screens from the starting point
  • Better responsive UI throughout all screens
What challenges did you encounter, and how did you overcome them?
  • Shadcn sheet component, used in the Mobile Navbar, did not close as intended. (Overcome: Had to look for a solution online and solve it)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • SmartAce•390
    @Smart-Ace-Designs
    Posted about 2 months ago

    Hello @GreccoOliva-Franco, Congratulations on completing the challenge.

    The mobile layout looks excellent and the mobile menu works perfectly. Good job! I also like how you used components effectively. I am not too familiar with React (I use Vue and Astro) so I can't really speak too much on the React code itself.

    Here are a few things I noticed that might need adjusting:

    1. The button, on hover, has black text on a black background.
    2. The aside and main articles section, for the titles of each article, do not contain a link or change colors on hover.
    3. The page has vertical scrollbar...not a huge deal but might be something to fix if you want.
    4. You might want to add some aria tags as needed, for accessibility purposes.

    Overall, just a few minor visual tweaks that you might want to adjust. But for the most part looks really good.

    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