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

Designo build with React+Typescript | TailwindCSS | react-hook-form

motion, react, tailwind-css, typescript, react-router
Zet•840
@zetmosoma10
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 feel proud for completing this Huge Multi-page website and i feel more motivated to build even more big project soon.

In this Project i worked with the following libraries

  • React+Typescript
  • TailwindCSS ( responsive design and styling the website)
  • react-router
  • react-leaflet ( rendering the Map and selecting locations)
  • react-hook-form ( tracking state of the form)
  • zod (schema base validation for form)
  • react-toastify ( send pop-up if form submission is successful )
  • react-helmet-async ( change page title dynamically when routing)
  • framer-motion ( add smooth animation when routing and toggling sidebar)
  • react-icons ( getting free svg icons)
What challenges did you encounter, and how did you overcome them?

Working with react-leaflet, it was my first time working with this library and i did not understand it at first. but eventually i manage to see the direction.

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

In mobile device , the sidebar is not appearing in Location page. i think my the Map has a highest z-index above all element on the page, but i dnt know how to reduce it or find another way to show the sidebar.

Thanks for any feedback.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    markus•2,720
    @markuslewin
    Posted 11 months ago

    This looks great!

    The map does indeed have a high z-index, but you could set the z-index of the sidebar to something even higher - like z-index: 1001 - to ensure it's displayed on top of the map.

    You could also isolate the the z-indexes of the map by setting isolation: isolate on .leaflet-container. That way, the high z-indexes only compete with eachother inside that container. That allows you to set a lower z-index on the sidebar, z-index: 1.

    Marked as helpful
  • Karol•3,100
    @VillageR88
    Posted 11 months ago

    You might want to switch from onSubmit to action, especially if you’re hosting on Vercel and then add real feedback messages with Nodemailer or something similar to give the project a bit of a backend touch.

    Marked as helpful
  • Karol•3,100
    @VillageR88
    Posted 11 months ago

    Great job, Zet! You might also want to style the autofill for input fields to match the regular input style.

    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

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