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

Intro section (Snap)

accessibility, bem, react, wordpress
GH0STZILLA•60
@GH0STZILLA
A solution to the Intro section with dropdown navigation 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?

This was the most complex project I've worked on so far, and I learned a lot about building and organizing a full multi-section website. I practiced creating a clean structure with semantic HTML5 elements and styled it using CSS Flexbox and Grid, which helped me create a responsive layout across different screen sizes.

I also worked on improving visual hierarchy, using font sizes, weights, and spacing to guide the user through the content. It was a great chance to think more deeply about user experience and how to keep the site both functional and visually appealing.

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

The hardest part was managing the layout across multiple breakpoints. I spent time making sure each section looked good on mobile, tablet, and desktop views. Ensuring that everything stayed aligned, spaced properly, and visually consistent was a real learning process.

Another challenge was keeping my CSS organized and avoiding code repetition. As the project grew, I had to be more mindful about class naming and reusability.

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

I’d love to get feedback on the following:

Overall layout and flow – does the site feel natural and easy to navigate?

Responsiveness – how well does the design adapt across devices?

Visual design – do colors, fonts, and spacing work well together?

Code structure – is there anything I could do to improve readability or reusability?

If you have suggestions on how I could improve UX or structure my code for future projects, I’d really appreciate it. Thanks so much for your time!

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 GH0STZILLA'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.