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

Responsive Designo agency website solution Using React JS & Typescript

accessibility, fresh, react, typescript, bootstrap
P
Krishna Vishwakarma•1,390
@KrishnaVishwakarma1595
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?

What I’m most proud of

I'm proud of how I tackled this project by building reusable UI components and optimizing them for different screen sizes. I focused on creating a responsive design that accurately reflects the challenge’s requirements while using modern CSS techniques like Flexbox and Grid to achieve the layout. I also made sure to implement robust form validation, ensuring a seamless experience for users across different device sizes. Additionally, leveraging TypeScript allowed me to keep the codebase clean and minimize bugs by enforcing static types, which contributed to smoother development and maintenance.

What I would do differently next time

If I were to approach this challenge again, I'd invest more time in refining animations and micro-interactions to make the UI even more engaging and intuitive for users. I would also consider implementing unit testing, particularly for reusable components, to catch potential issues early and increase reliability as the project scales. Finally, I would explore accessibility enhancements to ensure the website is fully usable for a wider range of users. This would include a focus on ARIA roles and improved keyboard navigation to enhance the overall user experience.

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

Challenges encountered

One of the main challenges I faced was ensuring the design looked consistent across various screen sizes. It required careful consideration of layout adjustments, especially for components with intricate designs like the service pages. I also encountered some complexities with form validation, particularly handling error messages dynamically based on user input, which had to be intuitive and user-friendly. Implementing type safety with TypeScript while ensuring flexibility in the components added another layer of complexity.

How I overcame them

To tackle responsive design, I used a mobile-first approach and leveraged CSS Grid and Flexbox to create a flexible layout that adjusts seamlessly. I spent extra time testing on different devices to ensure the experience was smooth across screen sizes. For form validation, I set up reusable validation functions, making it easier to manage and maintain error messages, and tested edge cases to make sure users received clear feedback. With TypeScript, I incrementally applied types, especially to props and states, allowing me to catch type mismatches early on while retaining flexibility in component usage. These steps made the codebase more robust and adaptable.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Krishna Vishwakarma'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.