Article Preview Component Master Challenge

Solution retrospective
I appreciate any feedback or suggestions helping me to improve my next challenge. Feel free to leave a comment.
Please log in to post a comment
Log in with GitHubCommunity feedback
- @Lescano713
Hi, your code looks great, but there are some areas where you can improve:
- HTML Structure: Consider using different semantic tags to group content based on its importance. For example:
<body> <main> <!-- For important content --> <section class="info-1"></section> <section class="info-2"></section> </main> </body>
You can take a look at this article for more information on semantic HTML.
-
Responsive: You can use both min-width and max-width properties to adapt your container to different screen sizes. Consider that some devices have widths as small as 320px, so your container should adapt accordingly to ensure a good user experience on various devices.
-
Consolidated Vendor Prefixes: Removed redundant vendor prefixes for border-radius and filter properties. Modern browsers generally don’t need these prefixes.
-
Used Shorthand Properties: Simplified border-radius properties and other CSS rules.
-
Consistent Units: Made sure units like px and rem are used consistently for sizing and spacing.
-
Improved Readability: Organized and formatted the CSS for better readability and consistency.
These changes help keep your CSS more manageable and easier to maintain.
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