Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 22 days ago

a modern CSS Framework like Bootstrap or Foundation.

jss, node, react, sql, pure-css
SuzalV•20
@SuzalV
A solution to the Blogr 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?

Proud of: I’m most proud of completing the Blogr landing page project with a fully responsive design across desktop and mobile views. I paid close attention to layout, typography, and visual balance, ensuring consistency with the original design mockup. I also utilized modern CSS techniques like Flexbox and Grid efficiently, improving structure and responsiveness.

What I’d do differently: Next time, I would manage my file organization and naming conventions better to keep the project more scalable and maintainable. I also realized I could improve performance by optimizing images and using semantic HTML more consistently. Additionally, incorporating accessibility features such as aria labels and proper contrast ratios would make the website more inclusive.

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

One of the main challenges I faced was making the navigation bar responsive, especially with the mobile hamburger menu. It was tricky to toggle the menu smoothly and ensure that dropdown links worked well across devices. I overcame this by reviewing documentation on responsive design patterns and testing with media queries and JavaScript event listeners until the behavior was consistent.

Another issue was aligning elements precisely as shown in the design mockup. Getting the background images and overlapping SVGs to appear correctly was difficult due to positioning conflicts. I resolved this by experimenting with absolute positioning and adjusting z-index layers carefully.

Lastly, I encountered a few browser compatibility issues, especially with flex and grid layouts behaving differently in Safari. I used browser-specific testing tools and fallback CSS properties to make sure the layout remained consistent.

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

I’d appreciate feedback on the following areas:

Navigation menu toggle (JavaScript logic) – I’m unsure if my current method for showing/hiding the mobile navigation is the most efficient or accessible. Are there cleaner or more accessible ways to handle this?

Responsive layout spacing – I struggled to maintain consistent padding and spacing between sections across breakpoints. Suggestions on improving spacing responsiveness without hardcoding values would be helpful.

CSS organization – I’d love input on how to better structure my CSS for scalability. Right now, my styles are functional but feel a bit messy and hard to manage.

Accessibility – Are there specific accessibility issues in my markup or missing semantic elements that I should address?

Performance optimization – The page loads fine, but I didn’t optimize images or minify CSS. I’d like advice on best practices for optimizing performance without overcomplicating the build process.

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