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

SunnySide Landing Page with HTML, CSS, and JS

Kelsey Hughes•80
@kelbri10
A solution to the Agency landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Coding the Sunnyside Landing page allowed me to practice various skills as it relates to CSS fundamentals and semantic HTML. I encountered a couple difficulties in this project, including making the hamburger menu, having the nav bar be responsive depending on screen size, as well as smaller issues such as the underline styling. When it comes to the hamburger menu, at first I tried using the "checkbox" hack, however the issue with using that solution is it raises accessibility concerns. I ended up using two elements with classes to identify which was to be used for what screen sizes (mobile vs. desktop) but I don't think that is optimized at all. For the middle images and text containers, I struggled to eliminate white space that would occur if the width was not set for the section. I definitely want to continue practicing creating a one to one copy of what is given because I know that in some aspects there are some deviations in styling. I think this is also affected by the lack of direct access to the Figma file which means that I'm eyeballing a lot of spacing. With more practice this will become easier. My biggest questions are related to responsiveness and making sure a decision is accessible. Something I read up on was aria-labels and I want to incorporate more accessibility features in my future submissions. Any feedback is welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Kelsey Hughes's solution.

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.