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

Intro component with sign-up form

AlexCristea2007•840
@AlexCristea2007
A solution to the Intro component with sign-up form 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’m most proud of my ability to stay focused and problem-solve effectively, even under pressure. For example, when working on a recent project, I was able to meet tight deadlines while maintaining the quality of my work. I’m also proud of my ability to collaborate well with others, especially when tackling challenging tasks.

Next time, I would try to delegate more tasks earlier in the process to allow more time for refining the details and conducting additional testing. I tend to take on a lot of responsibility, and while it’s rewarding, I’ve realized that sharing the workload can lead to even better results. This would also help me manage my time more effectively.

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

One of the biggest challenges I encountered was balancing multiple responsibilities, particularly when I had tight deadlines for both school projects and extracurricular activities. At first, it felt overwhelming trying to juggle everything at once.

To overcome this, I prioritized my tasks based on their urgency and importance, breaking down larger projects into smaller, more manageable steps. I also learned to communicate more effectively with my teammates and professors, asking for help or clarification when needed. By staying organized and focused, and by using tools like task lists and calendars, I was able to stay on top of everything and deliver quality work on time.

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

I would like help with optimizing the user interface and improving the overall user experience of the project. Specifically, I'm looking for advice on how to make the forms more intuitive and user-friendly, ensuring that validation and error messages are clear and helpful. Additionally, I'd appreciate feedback on how to implement better responsiveness across different devices, as well as suggestions on how to optimize the code for faster load times.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on AlexCristea2007'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.