Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 26 days ago

Room homepage ( with SASS, with vanilla HTML and JS)

P
BarrieDirk•540
@barriedirk
A solution to the Room homepage 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 improved my use of SASS.

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

The design takes some time to do.

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

Any suggestions will be welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Andrey•4,320
    @dar-ju
    Posted 26 days ago

    Hi BarrieDirk!

    Great work!

    I noticed a few details for improvement:

    • at a screen width of about 900px - 1050px the sections fly apart in height, check if it should be like this?
    • at a screen width below 900px when sliding in the first section the content in the second section jumps. Visually it is not very nice. This is due to the different number of lines in <p>, it is better to set this tag to something like min-height: 100px;
    • check the html code there are errors, for example the <title> tag is duplicated, link icon and so on. Also - An img element which has an alt attribute whose value is the empty string must not have a role attribute, this is an error

    Otherwise everything is great, you tried really hard!

    Marked as helpful
  • Harsh Kumar•3,350
    @thisisharsh7
    Posted 26 days ago
    • You’ve done a fantastic job implementing SASS and organizing your styles clearly. It’s evident that you have a good grasp of nesting and variables, which really helps keep the code clean and maintainable.
    • The overall layout looks great on desktop screens — well-structured and visually appealing.
    • To take this project to the next level, focusing a bit more on responsiveness would really enhance the user experience on different devices like tablets and mobiles. This will help ensure your design looks just as polished across all screen sizes.
    • Keep experimenting with media queries and flexible units like percentages or rem to improve adaptability.
    • Overall, your work shows a solid foundation and a great understanding of SASS. Keep up the awesome progress — you’re definitely heading in the right direction!
    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
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.

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