Design comparison
Solution retrospective
I am proud of being able to make the card component structure semantic and organized by separating it into clearly defined sections as follows: 1- card-image 2- card-content 3- card-info Which makes the code more readable and maintainable. As for what I would do differently next time, I really don't know exactly, but I am open minded for any suggestions if available.
What challenges did you encounter, and how did you overcome them?One of the challenges I encountered was finding suitable alternative text for the images used in the project. Providing meaningful alt text is crucial for accessibility, as it ensures that users who rely on screen readers can understand the content and purpose of the images. and for this issue, I found the file names for the images that provided with this project were descriptive and can be used as an alternative text.
What specific areas of your project would you like help with?I would value a thorough code review to ensure my HTML, CSS, and overall code structure follow best practices. Feedback on improving code readability and maintainability would be beneficial.
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