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

Responsive Ticket Generator (avatar change, name, and email)

Yuri Augusto Bernardes de Sousa•30
@yuriaugustobs
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?

I am proud to have made the site responsive for both desktop and mobile devices. Additionally, I enhanced the project and made some very cool changes, such as the avatar photo being updated with the user's uploaded file. I also translated all the text into my language and created a fictional name, and the ticket now comes with the correct name and email provided in the form. I believe I have significantly improved the project and overcome challenges.

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

One of the main challenges I encountered was ensuring the site was responsive across different devices. Initially, I designed the site with a 'desktop-first' approach, which made it difficult to adjust the layout for smaller screens. To overcome this, I used media queries to create a responsive design that adapts to various screen sizes. This process helped me better understand the concepts of media queries and the importance of prioritizing CSS changes based on device size. Additionally, I encountered issues with elements overflowing the viewport, which I resolved by carefully managing margins, padding, and using box-sizing: border-box to include padding and borders in the element's total width and height.

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

Responsive Design: Ensuring that the layout looks good on all devices, especially smaller screens. I have used a 'desktop-first' approach and media queries, but I am still facing some issues with elements overflowing the viewport and maintaining consistent spacing.

JavaScript Functionality: Improving the functionality of the gerarTicket function to ensure it works seamlessly. I want to make sure that the user input is validated correctly and that the ticket generation process is smooth.

CSS Optimization: Optimizing my CSS to avoid redundancy and improve performance. I want to ensure that my styles are organized and that I am using best practices for maintainability.

Cross-Browser Compatibility: Ensuring that the site works consistently across different browsers. I have noticed some inconsistencies in the layout and functionality when testing on different browsers.

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 Yuri Augusto Bernardes de Sousa'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.