Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Responsive landing page HTML CSS JavaScript

Stefan Grobler•150
@StefanGrobler78
A solution to the Agency landing page 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 made a triangle with css enjoyed this challenge, I enjoyed this challenge a lot it's trickier than what you might think. Try it you will see.

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

There was a lot challenges in this little challenge had to think real hard some places and play around a lot try to get to this version. Still not completely done but it's close.

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

I would love it if someone can give some idea's for animating slide out of the navigation menu Slide in is fine slide out have me stuck.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted about 1 year ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have a suggestion regarding your question that I believe will be of great interest to you.

    FIXING SLIDE OUT ANIMATION 🪄:

    • " give some idea's for animating slide out of the navigation menu Slide in is fine slide out have me stuck ", Well I'm here to share my thoughts with a working code!

    • First, the issue lies with using animation property because the moment we click the hamburger/button the slidein class is added. It contains the animation rule so the "slide-in" works because you only defined for sliding in and not for sliding out.

    • Second, You're using visibility rule for menu. So what i would like to suggest is to remove the animation "slidein" rule and add these rules,
    .ss__prim-navlist {
      visibility: hidden;
      translate: 100% 0;
      opacity: 0;
      transition: .7s ease;
    }
    
    .slidein {
      visibility: visible;
      translate: unset;
      opacity: 1;
    }
    
    • Here, we first setting the nav menu on "slide-out" position which is ready to be "slide-in" whenever the class slidein added for ul. Using these rules we can achieve a smooth-in-out sliding navigation as you wished!

    • Additionally we added opacity and transition to make it more visually appealing.

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    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