Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

React Interactive Card Details Form

react
Oscar Vaquera•270
@vaqueraoscar0
A solution to the Interactive card details form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Technologies

  • React
  • HTML5
  • CSS3

Project Details

The Interactive Card Details Form challenge turned out to be more challenging than anticipated, especially from a CSS perspective. I found it particularly difficult to handle the positioning of the credit cards and the accompanying information.

I'm uncertain if my approach to positioning the cards and the information was the most optimal solution. I would love to see how others have tackled this challenge and learn from their approaches. If you have any insights or suggestions regarding the CSS implementation, I'm open to feedback and eager to improve my skills.

Despite the challenges, I found this project to be a great learning experience. It pushed me to apply my CSS knowledge in a practical way and forced me to think critically about layout and positioning. I'm grateful for the opportunity to work on this project as it provided valuable insights into CSS techniques and best practices.

I have previously completed several intermediate and advanced coding problems, but this challenge posed a unique set of difficulties, particularly in terms of CSS. It served as a reminder that there is always room for growth and improvement.

Overall, I thoroughly enjoyed working on this project and gained valuable knowledge from it. It allowed me to enhance my CSS skills and expand my problem-solving abilities. I'm excited to continue learning and tackling new challenges in my coding journey.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Oscar Vaquera's solution.

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.