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

Learning NextJS and tailwind in this one.

next, tailwind-css, react
RicardoAymay•40
@RicardoAymay
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This project was a challange since I had trouble with many things I didn't expect. Adding the font was a problem by itself since there was a persistant fech error that didn't allow me to get the font. Somehow sill the font is a litthe different from the project.

Tailwind was complicated as it was my first contact. Not a major issue, but it took time for me to grasp it, especially regarding breakpoints. Also if someone can tell me if altering the styles using funcions is ok, I would appreciate the answer.

Forms were troubling to grasp, altough I had some knowledge, I insisted in the wrong path for some time intead of reviewing the basics.

The problems cited were great for me to understand more and made me more confident in my coding. Many aspects regarding best practices still remain, especially the conditional styling used. Altough there is still need for more refactoring, I think I have enough to submit the solution.

I am happy to have finished this, and expect the next challange to be easier because of what I learned here.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sean Hill•240
    @seanhillweb
    Posted over 1 year ago

    Great job! For your first Tailwind project, I think you have a good grasp of its capabilities. You mentioned in your comment about using functions for styling - are you referring to using media breakpoints?

    Tailwind has pretty good documentation about breakpoints and screen sizes, you can find that here:

    • https://tailwindcss.com/docs/responsive-design
    • https://tailwindcss.com/docs/screens

    Keep going! I think you have a solid understanding already.

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