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

Responsive Multipage Web Application in ReactJS

react, react-router, tailwind-css
P
Rohan T George•230
@19Rohan97
A solution to the Designo multi-page website 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 how I managed to solve the issue of routing with React Router when deploying the project on Vercel. Specifically, I was able to address the 404 error when navigating directly to routes like /about, which was caused by the static nature of Vercel’s hosting for React SPAs. By configuring the vercel.json file with rewrites to handle all routes through index.html, I was able to ensure seamless client-side routing.

Next time, I would focus on implementing better error handling for forms and consider adding more advanced form validation. I could also improve the responsiveness of certain sections for a smoother mobile experience.

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

One major challenge was handling the 404 error on Vercel when trying to access specific routes directly. Since React Router is client-side routing, Vercel's static hosting was not aware of the routes handled by React, resulting in 404 errors. I overcame this by adding a vercel.json configuration with rewrites, ensuring all routes are redirected to index.html. This allowed React Router to handle the routing properly and fixed the issue.

Another challenge was ensuring that anchor links (e.g., /locations#united-kingdom) worked both with route changes and page refreshes. I handled this by modifying the ScrollToTop component to check for hash-based navigation and scrolling to the appropriate section smoothly.

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

I’d love to get feedback on the following areas:

  • Error Handling: I would like to improve my form validation and error handling. Specifically, I'd like advice on implementing better UI feedback for users, particularly with multiple field validations.
  • Responsive Design: Although I've tested the design on multiple screen sizes, I'd appreciate suggestions on improving responsiveness, especially on larger screens (e.g., ensuring elements are well-aligned and look sharp).
  • Optimization: I’m interested in any advice on optimizing my React app for better performance, particularly in terms of load time and smooth transitions when navigating between pages.
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 Rohan T George'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

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.