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

SunnySide Agency Landing Page

Shuree•65
@shuree0331
A solution to the Agency landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I am having a tiny problem the nav section is not showing on the Safari browser on mobile. If anyone has any suggestion or solution, please help me. Thank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shuree•65
    @shuree0331
    Posted over 3 years ago

    Thanks all :-D

  • talentlessDeveloper•340
    @talentlessDeveloper
    Posted over 3 years ago

    @Shuree the nav on my device looks awesome, welldone.

  • Ven Gallardo•90
    @Gepeet
    Posted over 3 years ago

    Looking great for desktop view. Work even harder and you will master it eventually

  • Shuree•65
    @shuree0331
    Posted over 3 years ago

    @talentlessDeveloper and @Antonin Nhek, thanks for your feedback. I have looked at the problems and fixed them. I hope it will work fine now (fingers crossed). If you don't mind please check it on your devices and let me know if there is any problem.

  • talentlessDeveloper•340
    @talentlessDeveloper
    Posted over 3 years ago

    Hello Shuree, the desktop version looks good! I'm guessing there's no mobile version. Also the width of the nav overflowed on my desktop using 100vw instead of 100% made it work fine.

    welldone!

  • Shynn•235
    @0xShynn
    Posted over 3 years ago

    Hello Shuree, The safari mobile version is working meaning the nav section is visible, but you didn't implemented a mobile version right ? There's also a bug when desktop version is resized higher than 1440px (the stylesheet doesn't load or maybe the styles are locked up to 1440px)

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

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