Design comparison
Solution retrospective
I learned about semantics in html and why we should use them.
What challenges did you encounter, and how did you overcome them?Responsive queries,. I got problem in deciding whether I card width should be set by default or it should me made using what it is having inside.
What specific areas of your project would you like help with?Responsiveness Dynamic viewport resizing
Community feedback
- @danielmrz-devPosted 7 months ago
Hello @Vishal-Yadav-001!
Your solution looks great!
š Instead of using
<section>
as a container and<a>
as list items, it's recommended to use semantic HTML elements like<ul>
and<li>
for creating lists. This ensures that your code is more accessible, maintainable, and semantically meaningful.Here's how you can refactor your code:
Before Refactoring
<section class="social_btns"> <a>GitHub</a> <a>Frontend Mentor</a> <a>LinkedIn</a> <a>Twitter</a> <a>Instagram</a> </section>
After Refactoring
<ul class="social_btns"> <li> <a>GitHub</a> </li> <li> <a>Frontend Mentor</a> </li> <li> <a>LinkedIn</a> </li> <li> <a>Twitter</a> </li> <li> <a>Instagram</a> </li> </ul>
By using
<ul>
and<li>
, you convey the structure of your content more clearly, making it easier for screen readers and search engines to understand. Additionally, it aligns with best practices for HTML semantics.I hope you find this helpful!
Keep up the excellent work!
Marked as helpful0@Vishal-Yadav-001Posted 7 months agoThank you for great help, I will take care of this in future @danielmrz-dev
0
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