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

Interactive card using html , tailwind and javascript

Azimapata•90
@Azimapata
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 are you most proud of, and what would you do differently next time?

i am proud because i successfully created an engaging and interactive card that probably looks great and functions smoothly, which is a significant achievement. i overcame challenges in implementing the interactivity and getting the design just right, which would be something to be proud of.i learnt new techniques or improved your understanding of CSS, JavaScript, or other technologies, and applied them effectively in the project.

Next time i willconsider refactoring the code for better readability or efficiency. This could involve simplifying the logic, reducing redundancy, or using best practices more effectively, i will focus more on making the card accessible to all users, including those with disabilities, and ensuring it works well on different devices and screen sizes and add more features or improving the interactivity, such as animations or additional interactive elements.

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

Achieving a design that looks consistent across different devices and screen sizes could have been challenging, Implementing interactive features, like animations or dynamic content updates, might have been tricky, especially because it involved complex JavaScript logic, the user input (like form fields), validating and processing that input correctly might have been difficult.

i overcame it by doing some research, watched tutorials, consulted documentation to understand how to implement certain features or resolve specific issues, By testing my card frequently during development so that i could catch and fix issues early, making the final debugging process smoother.

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

Responsive Design, Interactivity,Performance Optimization and Accessibility on the card

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 Azimapata'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.