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

Responsive site made with Sass and pure JS

Grzegorz Sterczewski•680
@gsterczewski
A solution to the Room homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I'm open to all feedback and critique. I know that my scss could be more concise, and html is little too bloated, plus my approach to handle the slider controls positioning is hacky at the moment. Also,naming thing in english is a real struggle for me. I'm curious what do you guys think about the responsivness and breakpoints that I set ?. For anyone taking the time to check out my solution: thank you. Cheers.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hey, Grzegorz Sterczewski! 👋

    Good job! Your solution looks pretty good! 👏

    In addition to janez33's helpful feedback, I suggest,

    • Adding cursor: pointer to the mobile navigation menu icon.
    • Giving the slider buttons some more height in the mobile layout of the page to give the arrow icons inside them some space (as in the original design).
    • Preloading the slider images so that there is no delay between when the next slide is clicked and the image appears would be a nice touch!

    Keep coding (and happy coding, too)! 😁

  • Janez Kolar•140
    @janez33
    Posted over 4 years ago

    Hello I've looked at your solution :) I'm consider myself as a junior front-end developer and I have to say good job :) Here is one thing about responsivness - your solution doesn't look very good at 1000px viewporth width, there is too much white space at the bottom of the page. Setting media query to 1000px is not good for your solution I think and this is just my opinion. Your design doesn't look good on big screens from 1000px to 1600px. Width settings for .layout-wrapper doesn't do anything also height. Define your media queries before you start building the site (maybe look for some standard media queries you should always look) and then change positioning of the page to look good on those media queries and also device friendly. I hope I didn't say anything wrong. Keep building, every time you build something you are improving :) Regards from Slovenia

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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