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

Responsive Homepage built by HTML/SCSS/JS/jQuery

MetisT•275
@greatmetis
A solution to the Room homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I took 4 hours to complete this responsive homepage and to recap what I've learnt so far.

In this challenge,

  • I created an object in JS to contain information for slides, and I believe this makes my code look cleaner.
  • I also use <li></li> to create an indicator for image slide which is better user experience.

I hope you enjoy building code as I do, and I am always welcome any suggestions and collab opportunities.

Happy coding!☺️

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • tediko•6,700
    @tediko
    Posted about 4 years ago

    Hello, MetisT! 👋

    Great job on this challenge! I have a few suggestions to improve your solution:

    • I am not a big fan of these box-shadows. This is my feeling but i think in this specific project simpler is better.
    • You can easily rework your slider to be infinite. I mean, it won't stop after your reach last slide, but it will back to beginning of your slides. Try this code:
    $('.arrow-left').click(()=>{
        if(i>0){
            i--
            imageSlide(i)
            checkSlideState(i)
        } else if (i <= 0) {
            i = 2;
            imageSlide(i);
            checkSlideState(i);
        }
    })
    
    $('.arrow-right').click(()=>{
        if(i<2){
            i++
            imageSlide(i)
            checkSlideState(i)
        } else if (i <= 2) {
            console.log('hello');
            i = 0;
            imageSlide(i)
            checkSlideState(i)
        }
    })
    
    • Your padding on .upper-section .right is too big on mobile version, instead of 80px try for example with 20px so your content isn't missplaced.
    • The same problem occurs with .lower-section .middle-text. You can remove margin: 40px; from this element on mobile resolution.

    Good luck with that, have fun coding! 💪

  • MetisT•275
    @greatmetis
    Posted about 4 years ago

    Thanks @tediko for your time!!

    • I totally agree with you about the box-shadows. That is a try although it's unsuccessful experience, I learnt the lesson from this. I thought it could make the buttons more attractive, while apparently I even doubt my own decision. 😅

    • Thanks for pointing out the problem for the layout in mobile screen. I didn't see the misplace of those sections. It's big shame for me while I have edit them, and thank you😀

    • In terms of infinite slides, I have thought about it. While the reason why I added the indicator for the slide is to let users know the slide has been the end. However, I do understand loop the slide could be more user friendly. So, I decided to stick with you suggestion!

    To sum, I have learnt lots from this challenge, particularly the aspects of user-friendly and designer's eyes.

    Again, I really appreciate your time on my challenge!!

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 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

Oops! 😬

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

Log in with GitHub