
I used the flex display to help make it more responsive
Design comparison
Solution retrospective
I'm proud of the speed of completing the challenge, at the moment, I will still continue to study more about responsive websites. Although, with the tips from the last challenges, I managed to do a little better. Practice makes perfect.
What challenges did you encounter, and how did you overcome them?I didn't have any specific challenges. It was all natural in development.
What specific areas of your project would you like help with?More tips on css for responsive websites
Community feedback
- @MuhammadFarhanRosidiPosted about 2 months ago
When reviewing the solution provided by AndersonPaulo, here are some detailed feedback points to consider:
Semantic HTML
- Use of Semantic Tags: It’s great to see the implementation of semantic HTML elements like
<header>
,<nav>
,<main>
, and<footer>
. This helps improve the document structure and makes it more understandable for screen readers and search engines. Ensure that the correct level of heading tags (e.g.,<h1>
,<h2>
, etc.) is maintained for better accessibility and SEO.
Accessibility
- Alt Attributes: If images are present, ensure that all
<img>
tags have appropriatealt
attributes. This is essential for visually impaired users. - Keyboard Navigation: Check that all interactive elements are accessible via keyboard navigation (using Tab key) and provide focus styles for better visibility.
- ARIA Attributes: Consider using ARIA roles or properties where necessary, especially if there are custom controls or dynamic content. However, use ARIA sparingly and only when native HTML cannot achieve the desired accessibility.
Responsiveness
- Media Queries: Make sure there are responsive design features in place, like media queries, that allow the layout to adapt optimally to different screen sizes (mobile, tablet, desktop).
- Viewport Meta Tag: Ensure that the viewport meta tag is included in the HTML to control the layout on mobile browsers effectively.
Code Structure & Readability
- Clean and Organized Code: The code should be well-organized with appropriate indentation and spacing. Comments can help describe complex code sections to improve maintainability and readability.
- Reusable Components: If using a framework like React or Vue, ensure that components are reusable. Break down larger components into smaller, manageable pieces to promote better code reuse.
- Naming Conventions: Follow consistent naming conventions for classes and IDs, which makes it easier to understand the purpose of each element.
Visual Design
- Alignment with Design: Review how closely the implementation matches the original design specifications. Check for inconsistencies regarding fonts, colors, spacing, and overall layout. Any deviations should be justified and documented if they were made intentionally for usability or accessibility purposes.
- Testing on Different Devices: If possible, conduct testing across various devices and browsers to ensure that the design remains consistent and visually appealing universally.
Questions for Improvement
- What challenges did you face while implementing the layout? Understanding difficulties can help identify areas for further support.
- Have you tested the solution across different screen sizes? If not, it may be valuable to assess how the design adapts and address potential issues.
- Are there any particular areas of the code or design where you're seeking additional feedback? Clarifying specific areas of concern can yield more targeted advice.
Overall, the solution has the potential to be high-quality, but considering these feedback points will undoubtedly enhance its effectiveness and accessibility. Great job so far, and I look forward to seeing the improvements!
0 - Use of Semantic Tags: It’s great to see the implementation of semantic HTML elements like
Please log in to post a comment
Log in with GitHubJoin 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