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

#HTML #CSS #JS

adriantech-beep•390
@adriantech-beep
A solution to the Interactive card details form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

the most challenging part of this project is the implementation of the card number that has a format of a letter at the end.i'm a little bit confused on the result and the error message that says "wrong format, numbers only" but then on the output it should have a letter at the end.so i decided to follow the format that will be printed.

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

any suggestions or feedback on this project will be much appreciated.😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Lo-Deck•3,740
    @Lo-Deck
    Posted 8 months ago

    Hi well done for this challenge,

    I'll give this link you check out the mistake for HTML and CSS. 3WC validator.

    It's better to use em or rem instead of px. FreeCodeCamp. FreeCodeCamp.

    It's easier to start with a mobile-approach FreeCodeCamp.

    I don't know what do you mean with the letter at the end, when you look at the challenge, it's an example for the active state. It's when you display an error.

    And it's better to use rem or em for the font-size with my screen the text goes out of the card, try with the webtool and a size above 2200.

    Hope to be helpful.

    Marked as helpful
  • adriantech-beep•390
    @adriantech-beep
    Posted 8 months ago

    @lo-deck thank you for this kind of suggestion.rigth now i'm still practicing on the responsiveness and still a little lost.i will implement this kind of approach to make it more better.thank you.happy coding.❤️

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