Design comparison
Solution retrospective
all feedback is welcome thank you
Community feedback
- @danielmrz-devPosted 10 months ago
Hello @sefianeouberka!
Your solution looks great!
I have a couple of suggestions for improvement:
- First: In order to make your HTML code more semantic, don't skip heading levels - start with
<h1>
, then use<h2>
, and so on.. Unlike what most people think, it's not just about the size and weight of the text.
π The
<h1>
to<h6>
tags are used to define HTML headings.π
<h1>
defines the most important heading.π
<h6>
defines the least important heading.π Only use one
<h1>
per page - this should represent the main heading/title for the whole page.- Second: Still about semantic HTML, use
<main>
to wrap the main content instead of<div>
.
All these tag changes may have little or no visual impact but they make your HTML code more semantic and improve SEO optimization as well as the accessibility of your project.
I hope it helps!
Other than that, great job!
Marked as helpful0 - First: In order to make your HTML code more semantic, don't skip heading levels - start with
- @HunigoleSanPosted 10 months ago
Hello @aykinsancakli! π
I want to commend you for your outstanding work, which closely aligns with the challenge requirements. Allow me to offer a suggestion that could enhance your CSS approach. π οΈ Upon reviewing your code snippet:
.btn:hover { background: var(--color) }
It's evident that you effectively utilize the hover pseudo-class, particularly suited for PC devices. However, it's crucial to acknowledge potential issues on mobile devices where hover behaves differently, often leading to unexpected outcomes. π± To address this, I recommend deactivating hover for mobile devices and utilizing the active pseudo-class instead. π
@media (max-width: 414px) { .btn:hover { background: none; /* Define the desired background for the button in its normal state */ } /* Mobile styles */ .btn:active { background: var(--color) } }
You have the flexibility to employ this approach or explore alternative methods that better suit your preferences. The key takeaway is to gain insights into the nuances we must consider to refine our coding practices. π οΈπ
Marked as helpful0
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