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

Interactive Card Details Form using HTML, CSS and JavaScript

Lahan•210
@lahanhelith
A solution to the Interactive card details form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey there Frontend Community!

I finished another solution today but I'm not truly proud of it yet since it was a struggle to get the CSS to look like the design.

I mainly struggled with getting the cards positions to change according to the size of the screen which created layout issues in the solution.

After a while of brute forcing and adding margin values here and there i managed to make it look okay on screens but I'm not truly proud of that part. I did lookup things but almost none of the resources helped with my situation.

I believe I'm going through the tutorial hell phase since I really couldn't understand what went wrong so I plan on going for simpler projects and try improve my CSS fundamentals and come back to this project.

Any resources that might help are appreciated which also includes Feedback!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Amr mohamed•370
    @AmrAbdelgwaad
    Posted over 1 year ago

    Hey Lahan

    I did this project before and I did the mobile version only because it depends heavily on position: absolute: I've done a GURU challenge and the HTML and CSS of it were way easier than this challenge, you are already out of tutorial hell continue building projects and you will get better, I have a couple of comments for you in this project:

    • You shouldn't use IDs to style your elements click here to know more

    • Media query should be in ems or rems and do the mobile version first PX, EM or REM Media Queries?

    keep it up and continue building projects cheers🎉

    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

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