Responsive Landing Page

Solution retrospective
Next time i would style the footer differently. I will use more flex and grid layout more in the footer instead of trying to margin-inline: auto. Now that i think back, i wonder which approach is better between trying to style 3 viewports (mobile, tablet and desktop) at the same time and finish one viewport and then move on to the next.
What challenges did you encounter, and how did you overcome them?I have encountered the problem with CSS nesting. The CSS nesting worked while i was in developing phase but when it comes to production build, it didn't. I have spent some time to figure out what went wrong and ultimately, it was because of CSS nesting. I had to refactor all the CSS nesting. I hope in the future, CSS nesting will be more widely supported.
What specific areas of your project would you like help with?It was the background image. There are two problems that really make me struggle. The first one is adding background image and make it appear under the content. The second problem is that with different viewports, those background images need to be positioned differently and have different sizes. Thats not all, the wider the screen, the visual will also change.
Please log in to post a comment
Log in with GitHubCommunity feedback
- @Ayokanmi-Adejola
I've had a detailed look at your Responsive Landing Page solution, and it's a truly impressive piece of work! You've done an excellent job bringing this multi-section design to life.
What I Liked :
- Exceptional Responsiveness: The landing page adapts beautifully and smoothly across various screen sizes, from large desktops down to mobile devices. The layout transitions are well-handled, and the content remains perfectly readable.
- Strong Visual Fidelity: The design, colors, typography, and overall aesthetic are very accurate to the Frontend Mentor specifications. The different sections are clearly defined and visually appealing.
- Clear Call-to-Actions (CTAs): The buttons and interactive elements are prominent and guide the user effectively.
- Effective Layout Techniques: Your implementation demonstrates a solid understanding of how to build complex, responsive layouts, likely utilizing modern CSS like Flexbox and Grid.
Areas for Improvement :
-
HTML Semantics & Structure:
- Review your heading structure (
<h1>
,<h2>
,<h3>
, etc.). Ensure there's a clear hierarchy throughout the page, with one primary<h1>
for the main title of the page/hero section, and then<h2>
for major sections, and<h3>
for sub-sections. This is crucial for SEO and screen reader navigation. - For elements like the navigation, footer links, or feature lists, ensure you're using appropriate semantic HTML (e.g.,
<nav>
for navigation,<ul>
and<li>
for lists of links/features). - All images (
<img>
tags) should have descriptivealt
attributes (e.g.,alt="Illustration of dashboard statistics"
instead of just "dashboard"). This significantly improves accessibility for screen reader users.
- Review your heading structure (
-
Accessibility (beyond
alt
attributes):- For interactive elements like the mobile navigation toggle (hamburger menu), ensure it's a
<button>
element. If it's adiv
, it needsrole="button"
,tabindex="0"
, and JavaScript to handleEnter
andSpace
key presses. Also, consideraria-expanded
andaria-controls
for accessibility. - Double-check color contrast ratios for all text against its background. Ensuring high contrast (WCAG AA standard or better) is vital for readability, especially for users with visual impairments.
- Ensure keyboard navigation is smooth for all interactive elements (links, buttons). All elements should be reachable and usable with just the
Tab
key andEnter
/Space
.
- For interactive elements like the mobile navigation toggle (hamburger menu), ensure it's a
-
CSS Best Practices & Organization:
- Consider using CSS Variables (Custom Properties) for all your colors, font families, common spacing values, and potentially reusable component styles. This will make your stylesheet much more maintainable, scalable, and consistent.
- Review your CSS for any highly specific or deeply nested selectors. Sometimes, flatter selector structures are easier to read, maintain, and prevent specificity issues.
In Summary: This is a truly impressive Responsive Landing Page, TanLuc2410! You've clearly demonstrated a strong ability to translate a complex design into a well-adapting web page. Focusing on refining the HTML semantics and further enhancing accessibility will make your solution even more robust and user-friendly for everyone. Keep up the fantastic work!
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