Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Conference Ticket Generator with React and Tailwind CSS

react, react-router, tailwind-css, vite
Diego QR•50
@DiegoQR
A solution to the Conference ticket generator 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?

This was my first project to submit to Frontend mentor and to practice some React with conjunction with tailwind since i recently learned how to use it and i wanted to see how useful the tool was and i had to admit that is a powerful tool

Also went for a little self challenge to not use any external UI Library and to create my own component library for this specific project

The element that cost me more to develop was the drag and drop element, since i am used to just import an drag an drop from an UI library and to learn how the Drag and drop API works in html was a challenge in this project. In the end with the help in the MDN Documentation and using Copilot and DeepSeek to understand how to implement this function i managed to go, for what i think, a satisfactory result

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

Some things I want to improve an get better on are the code legibility and mantenible i understand i could decouple some functions or elements in the InputDragAndDrop.jsx and specially in the Form.jsx.

Also i want to start getting the habit of doing the test cases first and implementing automatic tests to assure the QA of the page, since i been having bugs almost every time i started to develop a new feature, some bugs there is to correct are the buttons remove and change image in the drag and drop and the fact that when you drop an image all the form resets.

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

Specially how to make the code more clean and modular, i think that the reason for some bugs happening in the app is specially for the form re-rendering for changing states in the Drag and drop part.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Diego QR'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 1st-party linked stylesheets, and styles within <style> tags.

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.