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

Responsive News Landing Page using ReactJS

react, vite
Okpalannajiaku Xavier Chimezie•50
@TheRedHoodGuy
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 am most proud of successfully completing my first React-App project, which was a significant milestone in my learning journey. I am proud of the collaboration with Ayomikun, which not only enhanced the project's quality but also provided a valuable learning experience. The project's completion is a testament to our perseverance and resilience in the face of challenges.

If I were to do this project again, I would focus more on code organization and modularity from the onset. While the project's functionality is sound, I recognize that the code structure could be improved for better maintainability and scalability. Additionally, I would invest more time in testing and debugging to ensure a more polished final product.

What challenges did you encounter, and how did you overcome them?

During the project, I encountered a few challenges, including issues with state management and component rendering. To overcome these challenges, I utilized online resources, such as the official React documentation and Stack Overflow, to find solutions. I also worked together with my collaborator to debug the code, sharing our understanding of the issues and potential fixes. This collaborative approach allowed us to overcome the challenges and deliver a functional project.

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

I would appreciate feedback on how to improve the project's code organization and structure. Specifically, I am interested in learning about best practices for breaking down a React application into manageable components and modules. Additionally, I would like guidance on how to enhance the project's performance, potentially through optimization techniques or the use of libraries like React Query. Overall, this project has been a valuable learning experience, and I look forward to continuing to improve my skills and knowledge in React development.

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 Okpalannajiaku Xavier Chimezie'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.