Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 18 days ago

Conference Ticket Generator using React + Tailwindcss

node, react, vite, tailwind-css
Bankole David•380
@BANKOLEDO
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?

Honestly, I’m really proud of how I brought this project to life using React and Tailwind CSS. I took the original plain HTML/CSS/JS version and restructured everything into clean, reusable components—while still keeping the feel of the original design. I made sure it works well on all screen sizes, added form validation, drag-and-drop upload, and made the ticket preview dynamic and user-friendly. It feels good to see it all come together the way I imagined. If I were to do it again, I’d work more on performance—especially around image loading, like the SVG ticket background. I’d also love to add smoother transitions or micro-animations to make the experience feel more polished. And maybe even explore adding basic tests to catch bugs early and make sure everything works for everyone, including those using assistive tech.

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

One of the biggest challenges was translating the static HTML/CSS/JS project into a fully dynamic React setup without losing the original layout and behavior. Getting the background images, pattern overlays, and ticket design to render correctly across devices took a lot of tweaking—especially with Tailwind’s utility classes and responsive breakpoints.

Another tricky part was handling the image upload. I wanted the form to feel modern, so I implemented drag-and-drop, preview, and validation. Managing the file state and error handling in React required a lot of trial and error, but I broke things down into smaller components, tested each part, and used helpful feedback messages to improve the UX.

Lastly, styling issues like overlapping z-index elements and weird spacing across viewports gave me a few headaches—but debugging with DevTools and slowly layering things helped me resolve them one by one.

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

i would love feedback on how to further optimize the ticket section, especially when it comes to background image performance and load time. I'm also open to suggestions on improving accessibility and how to make the form more intuitive for keyboard and screen reader users.

Another area I’d appreciate help with is animation and user feedback—how to make transitions smoother without overloading the UI. And lastly, if there are better ways to structure or refactor my React components for scalability, I’m all ears!

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 Bankole David'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

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.