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

Using HTML, CSS to completed.

雷楲𨛵(Wei-Hu, Ley)•210
@DerRight
A solution to the Huddle landing page with a single introductory section 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 pride myself on finding a way to work with HTML and CSS that allows me to finish my work faster!

※Completion time: 1 hour 28 minutes

我自豪於找到一個適合的方式來製作HTML和CSS,會讓我更快的完成作品!

※完成時間:一小時二十八分鐘

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

This question is more like reviewing how to use components and grammar!

這一題更像是在複習怎麼使用元件和語法!

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

Hello, first of all, thank you for coming to see my finished product! There may be some unfamiliarities in grammar, such as the CSS layout design, and I feel like I need more practice!

您好,首先先感謝您前來觀看我的成品! 對於語法上還有一些可能比較生疏,比如說css的版面配置上的設計,感覺還要更加練習才可以!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Md Irfan Rahman Mubin•210
    @Md-Mubin
    Posted 3 months ago

    Remember when you use images in css always use, background-position: center; // for make it center background-repeat: no-repeat; // for render it only one time background-size: cover; // make the img cover the full screen

    in your output the background img is repeating.

    Marked as helpful

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub