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

Fully Functional and Accurate - Mobile and Desktop Design.

vcgmuse•70
@vcgmuse
A solution to the Age calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Take a look, try to break it. Please let me know if you do or if you notice something that would make it better.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Narciso Lobo•20
    @narcisolobo
    Posted over 1 year ago

    Excellent job, my friend! Would love to see the card centered vertically as well as horizontally -- the solution provided by Daniel above will work well.

    Would also love to see a hover state on the button, as Mudassar suggests.

    To make the solution more accessible, please use a label instead of a paragraph for the form elements. The label should have a for attribute that matches the id attribute of the input it's paired with.

    Also, your alt attribute is empty for the button. I suggest filling that in with "Calculate Age" or something to that effect. That will also help with accessibility.

    Marked as helpful
  • P
    Daniel 🛸•44,810
    @danielmrz-dev
    Posted over 1 year ago

    Hello @vcgmuse!

    Your project looks great!

    I see that you already got help here, but there's something that is yet to cover:

    I noticed that you used margin to place the card in the middle of the page. That's not the best way and depending on the screen size, your card won't be centered. So here's a very efficient way to center the card:

    • You can apply this to the body (in order to work properly, you can't use position or margins):
    body {
        min-height: 100vh;
        display: flex;
        justify-content: center;
        align-items: center;
    }
    

    I hope it helps!

    Other than that, you did an excellent job!

    Marked as helpful
  • Mudassar Majeed•160
    @mudasarmajeed5
    Posted over 1 year ago

    Yes, your solution is perfect, the logic building is perfect, but I would suggest giving specific width and height of the card for PC and laptop users because on my browser it's taking full width and the card looks a bit un-natural. You can Improve it further i.e. setting width and height to 600px and 400px, further you can add cursor:pointer; when we hover over the SVG, and you can set the opacity of the SVG to 70%, when we hover it should be set to 100% using CSS with a smooth transition to give it a feel of a button.

    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