Responsive Ticket Generator (avatar change, name, and email)
Design comparison
Solution retrospective
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.
Community feedback
Please log in to post a comment
Log in with GitHubJoin 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