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

Conference Ticket Generator built with Angular šŸ…°ļø

angular, sass/scss, typescript
P
Daniel šŸ›øā€¢44,740
@danielmrz-dev
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?

šŸ›ø Hello FEM Community! I'm Daniel and this is my solution for this challenge! 😊

šŸ› ļø Built with:

  • Angular šŸ…°ļø
  • SASS šŸŽØ
  • TypeScript šŸ¤–
  • BEM Notation šŸ…±ļø
  • Third Party API (Github Users) šŸ†•
  • Mobile first workflow approach šŸ“²

Nice project! I've added an async validator for the github username field. So when you type your username, it makes a HTTP request to Github Users API to check if that's a real username. I wanted to practice this topic a little bit so I added it.

I've never worked with a File input, so I struggled a litte bit to add the validations to it, but I think the final result is quite good. I tested it a lot before submitting this solution.

It took me a few days to finish, specially because of the end of the year, but I enjoyed every minute of it.

Again, thanks to the Front-End Mentor team that creates challenges that make us learn a lot from doing them. šŸ’Ÿ

If you have any suggestions on how I can improve this project, feel free to leave me a comment!

Feedback welcome 😊

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 Daniel šŸ›ø'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.