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

DHBLee_Space Using HTML, SCSS , JS

P
Dong Hee•1,290
@DHBLee
A solution to the Space tourism multi-page website 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 proud that I was able to finish this website faster than I expected. Although It would've been much faster if I did things properly at the beginning. So I will do my base codes different next time

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

It was my first time using a figma design to implement the challenge and it really helped me a lot. However, the extra information figma gave made me struggle a lot when it comes to padding and margin. Since I can now see the values of their spacing, I tried to replicate it, and that led me to hard code all my containers and images :D.. D: So I overcame it by hard coding it, which is not good.

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

I would really like help with how the padding and margin work in this challenge, and the corresponding html structure or CSS styling to achieve it. I'm also having a hard time maintaining the size of the images when I'm using 100%, that's why I had to use clamp as its width.

Tenkyu very much!

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 Dong Hee'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.