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

Html, Sass, Vanilla Js to recreate the room homepage challenge

Onyekwere Precious•755
@Yellow-May
A solution to the Room homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I am curious about the most effective way to set the images I had problems with getting my images to look as clear as in the example.

An contribution would be appreciated, thank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aleksandr Aksenov•750
    @axevldk
    Posted over 4 years ago

    Hi, Onyekwere Precious ~ I have studied your work, and here are some of opinions.

    First, you mentioned about image, and yes, that doesn't look good for now. You can add css property to main.showcase section:nth-child(1) .section .img-section img { object-fit: cover; }. It will improve image vision. Or you can make them background image of wrapper. That's the way I love.

    And I found out there are 13 accessibility errors. You can eliminate them by adding name or title attributes to items. And you may have to add width attribute to images that have srcset attribute.

    Hope this will help you even a bit. Happy coding ~

  • Madison Weber•110
    @MadisonWeber
    Posted over 4 years ago

    Hey i really like the look of your site. The way the text flows down on the slideshow and then rewinds to the start is really cool. Only thing a little bit confusing for me is if i hit the right arrow you get the picture coming from the left, which for me is not what i would expect. I would think inherently if the user hits the right arrow they would expect to go to the picture on the right of the slideshow.

  • positivevibes•205
    @posivibez
    Posted over 4 years ago

    Nice work, I'm currently working on the same project. Kinda minor but how are you having the underline animation on the nav links scale out from the center. I'm trying looking in dev tools but don't see how you are doing that. My underlines are scaling out from left to right. Thanks and good work!

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

Oops! 😬

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

Log in with GitHub