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

Built with NextJS, Tailwind CSS, and Typescript

accessibility, next, react, tailwind-css, typescript
solvman•1,650
@solvman
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 made an effort to take this project to the next level by implementing several things that were not required but would harden my knowledge and give me additional practice:

  • ⭐️ Made this project a bit harder by implementing an external data feed. I created a data type for the article object and stored the articles in an array separately, allowing me to simulate how a real-world news site would have it.
  • ⭐️ Abstracted the business logic of pulling the most popular, newest articles and the featured into separate hooks. By the way, it required expanding the article object to add rank and publish date.
  • ⭐️ Implemented a design system through CSS global variables, making it possible to theme this project down the road if needed. It all included not only colors but also spacing and fonts.
  • ⭐️ Implemented fonts and space fluid sizing using the clamp CSS function, allowing smooth expansion and contraction with the viewport's size.
  • ⭐️ Crafted a fully accessible mobile hamburger slide-out drawer, which included locking scroll ability for underlining content, limiting the ability to tab only to mobile slide-out drawer, and making all button aria accessible by adding screen reader-only labels.
What challenges did you encounter, and how did you overcome them?

The most challenging task was different from what I expected. 🤓 I tried to lay out all of the items for the desktop design using a flexbox, which proved to be very challenging in aligning the bottom section with the featured article. 😅 However, I quickly realized that I was taking longer than I should have and switched to a CSS grid, which let me quickly lay out the desktop version. 🤩🎉🎊

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

Any feedback is highly appreciated! 🫶

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on solvman's solution.

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.