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

Using HTML, CSS and JavaScript to completed.

雷楲𨛵(Wei-Hu, Ley)•210
@DerRight
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 how I was able to write this in such a quick time even though I hadn't programmed in a while!

我最自豪於即使我已經有一段時間沒有寫程式了,還可以在快速的時間內寫出來!

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

The most difficult part for me was how JavaScript handled the wrong icon and message, because I didn't expect it to only read the first one and ignore how to write the syntax. In the end, I relied on chatGPT and the file to complete it.

對於我來說最困難的地方是JavaScript要處理錯誤的icon和message的地方,因為我沒有想到他只會讀取第一個而忽略了語法要怎麼寫,最後依靠chatGPT和文件才完成。

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

Hello everyone, first of all, thank you for coming to see my work! I hope to get some advice on JavaScript, as I am not very proficient in it.

各位前輩大家好,首先先謝謝您來看小弟的作品! 希望可以在JavaScript上可以獲得指教,因為對於JavaScript還是不太熟練。

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 雷楲𨛵(Wei-Hu, Ley)'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.