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

Interactive card details form | HTML, SASS, Vanilla JS

bem, sass/scss
Eduardo•910
@KTrick01
A solution to the Interactive card details form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was a challenging one for me, it was kinda hard to do all the validation, but at the end, I did it (thanks stack overflow), making the cards was harder than I thought, but thanks to that I learned how to overlap elements with CSS grid, so yeah, after all it's a pretty fun challenge!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hey Eduardo, this was well done I think, and yes, great job with the validation! It was able to detect the year number input I entered was invalid, which is good 😄

    Two thoughts I have when playing around with this:

    1. You mentioned about positioning being difficult (well for me it's difficult almost every FEM challenge 😅). I see that the cards shift in the mobile view when the browser size is changed, and I also see that you used the purple background as the body background instead, and so in the mobile view, I can especially see how the cards are separated from the background. Have you tried using just two containers, and not putting the purple on the body background? That way, you might be able to have the cards in the left container for desktop view and still have the cards be positioned in relation to the container rather than leaving the container when the browser size shifts. I think that's something I would try when I attempt this challenge.

    2. I see that you added a green outline for the validation as well; I don't know whether that's part of the challenge or not since I don't remember seeing it in the other solutions I saw, but in any case, it's a bit bright, and as a user I think it's enough to see just the red, in that, you'd want the user to only focus on what is the problem and fix it; for me, it's not too necessary to show the green outline since there's no problem with it and no need to focus on it.

    That's all I have for now, great job putting everything together, and I'm glad you learned lots from Stack Overflow!

    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