Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Manage Landing Page built with SASS & Swiper.js for slider feature

sass/scss
Nyrell Leonor•400
@nyrellcl
A solution to the Manage landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Been meaning to finally finish this project. It served as great practice for creating landing pages. The desktop and mobile version for the footer was a bit frustrating to get right since most of the elements were designed and placed in very different orientations. But I was able to get it right eventually!

I also decided to use swiper.js for the slider feature for efficiency, though I would go back and implement the slider via vanilla JS just for practice and to get comfortable with JS even more.

When reviewing my code, I REALLy appreciate any suggestions on how to make it better, concise, and easy to read.

As always, any feedback is greatly appreciated. Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ERIGO Chigozie Nicholas•650
    @nick335
    Posted almost 3 years ago

    Hello NYRELL LEONOR’S,

    Great Job with the challenge! noticed you didn't implement the background images if you had issues with it, this is how you resolve it:

    // normally you do this
    
    background-size : cover 'or' contain;
    
    background-position: center 'or' Top 'or' Left 'or' Bottom 'or' Right;
    
    //but to accurately position it you can try this!!
    
    background-size: 300px 100px; 'which is the width and height';
    
    background-position: top 100px  right 100px; //the same can done for the bottom and the left
    

    Hope this was helpful,

    Happy Coding

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