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

Completed with NestJS, TailwindCSS, RHF, Framer Motion, and DayJS

accessibility, lighthouse, next, tailwind-css, motion
solvman•1,650
@solvman
A solution to the Age calculator app 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'm proud of my work validating the actual dates, including leap years and days within each month. I utilized an awesome small DayJS library for that. Excellent find!

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

The most challenging task was to figure out how to revalidate different interdependent fields using the React Hook Form package. After some research, I realized I could utilize the trigger() function provided by useForm(). I added that function to onChange() so that every field could have dependent fields revalidated.

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

I would love to have feedback on my coding style. Any suggestions for improvement or criticism are highly welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Michel•60
    @michelNice
    Posted 12 months ago

    Hi everyone,

    I’m working on a responsive navigation layout and could use some assistance. Here’s what I’m aiming for:

    On desktop: The logo should be on the left, and the navigation should be on the right side with the shopping cart as the last item in the navigation list. On mobile: The logo remains on the left. There should be a shopping cart icon in the center, and a clickable hamburger menu that changes to a close "x" when clicked. When the hamburger menu is clicked, the navigation should slide down from the top. You can check out my current setup and what I’m working towards through the following links:

    GitHub:https://github.com/michelNice/Partiu-Russia

    my website: https://nimble-genie-a7cc7e.netlify.app/

    what I am trying to do: my website:https://partiurussia.com.br/

    Any help or guidance on achieving this would be greatly appreciated!

    Thanks!

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