Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Responsive designo-multipage-website using NextJS & TailwindCSS

next, tailwind-css
Laharl•1,000
@UrbanskiDev
A solution to the Designo multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello FrontendMentor community !

It has been a little while since the last challenge I completed. I took my time on this one, since it is quite a big one (I took a break for 1 weak, which delayed a bit the challenge), even if at first sight, I wasn't really sure I would succeed it. I also used technology I never used before like NextJs or Figma, and I was a bit lost at first. I think I could have done better with the component system of NextJs, but since it was my first time using NextJs, I feel proud of the result. Using Figma was really a great experience, it makes the work way easier than it is to guess with a base image.

About the challenge, it was really fun, it allowed to practice a lot of things, flex, grid, decorative hover effects, the usage of Leaflet, a really basic form validation (which could be improved), the mobile hamburger and more importantly, the responsive of the website, with many other things on the road. There's some details I wasn't really sure to add or how to do them, for example the circle design on the background of most pages, I thought of using position relative/absolute, but... I'm not really convinced it is the best way to proceed.

Globally, I'm really proud of the results I have got, looks pretty and couldn't hope any better than that. I'm still open to suggestions and feedbacks, since I know for sure it is far from being perfect.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

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