Skip to content
Submitted 8 days ago

blog-preview-card-main

LaibaRana10•70
@LaibaRana10
Preview site (opens in new tab)View code (opens in new tab)
This is a solution for...Blog preview card
  • HTML
  • CSS
1newbie

Design comparison

SolutionDesign

Solution retrospective

What are you most proud of, and what would you do differently next time?

One of the things I am most proud of in this project is my ability to bring the design to life with clean and structured code. I paid close attention to detail, ensuring that the layout, typography, and colors matched the given design perfectly. Additionally, I improved my CSS skills, especially in creating a responsive and visually appealing user interface.

What I Would Do Differently Next Time If I had to do something differently, I would focus more on planning before coding. At times, I found myself making multiple revisions because I hadn’t fully structured my approach beforehand. Next time, I would take the time to break down the project into smaller steps, sketch a layout plan, and write pseudocode to streamline the development process.

By learning from these experiences, I can continue to improve and build even better projects in the future!

What challenges did you encounter, and how did you overcome them?

Challenges I Faced One of the biggest challenges I encountered in this project was ensuring responsive design across different screen sizes. While testing on various devices, I noticed that some elements weren’t aligning properly, and there were occasional overlapping issues. Additionally, understanding the proper use of CSS Flexbox and Grid for complex layouts was a bit tricky.

How I Overcame Them I adopted a mobile-first approach, designing for smaller screens first and then adjusting for larger devices. I used browser developer tools to inspect and debug styling issues at different breakpoints. I practiced more with CSS Grid and Flexbox, referring to documentation and tutorials to improve my understanding. I tested my website on multiple devices to ensure a smooth and consistent user experience. These challenges were tough, but they helped me learn and improve, especially in building responsive and well-structured designs

What specific areas of your project would you like help with?

Areas I Need Help With While working on this project, I identified a few areas where I could use some guidance to improve my skills and make the final product even better:

Responsive Design – Although I have implemented a mobile-friendly layout, I would love feedback on how to refine my approach and make it even more seamless across different screen sizes. Code Optimization – I want to ensure my HTML, CSS, and JavaScript are well-structured, efficient, and easy to maintain. Any tips on best practices would be appreciated! Animations and User Interactivity – I’d like to enhance the user experience with smooth animations and subtle interactive elements, but I’m unsure of the best techniques to achieve this effectively.

Community feedback

  • Zahra Ehsani•100
    @ehsanidevPosted 8 days ago

    Issues in your Code:

    1. In the auther section, the class name is used twice (once for p and once for img). This could cause confusion.

    2. In the <p class="learning"></p>Learning</p> section, the <p> tag is incorrectly closed (an extra </p> is present).

    3. The media query @media(max-width:1850) is not written correctly. It should be @media (max-width: 1850px).

    4. In the :root section, the color --Gray is defined twice, and one of them should likely be --Black.

    5. The code could benefit from more comments to explain complex sections or logic.

    6. The media query is not well-defined and may not work as intended for responsive design.

    7. The use of overly specific selectors (e.g., .card .auther img) could lead to maintainability issues in larger projects.

    8. Some values (e.g., top: 15px, right: -15px in .card::before) are hardcoded, which might not be flexible for different screen sizes or layouts.

    9. There is no alt text for the second image in the auther section, which could impact accessibility.

    10. The .attribution class and its styles are commented out in the HTML but remain in the CSS, which could lead to unnecessary code bloat.

    Marked as helpful
    0

Please log in to post a comment

Log in with GitHub

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