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 Ping single column coming soon page 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 of the fact that I was able to quickly learn and write the Javascript because of my previous experience.

※Completion time: 1 hour and 30 minutes.

我自豪於這次的Javascript因為前面的經驗,所以很快就可以上手並且寫完。

※完成時間:一小時三十分鐘。

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

The challenge for me is that I haven’t written any programs for nearly four months, so I’m no longer familiar with many syntaxes. I need to spend some time to slowly get back in control!

對我來說的挑戰是因為我有將近四個月的時間沒有寫程式了,所以對於很多語法都生疏了很多,需要再花時間慢慢找回手感!

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

First of all, thank you for coming to see my finished product. I already have a certain degree of understanding of using HTML, CSS, and Javascript, but I want to learn more other syntaxes, such as sass, bootstrap 5, etc.

首先,謝謝您前來觀看我的成品,對於使用HTML、CSS、Javascript已經有一定程度的了解,反而是想要學習更多其他語法,像是sass、bootstrap 5等。

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 雷楲𨛵(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.