Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Blog preview card submission

Vĩnh Bảo Phúc•40
@kevinphuc
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I have improve a lot from the first exercise.

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

I have a problem when deploy in page.github.io that the image was not deployed along with the code while I did not adjust any path of any image. When I run on my localhost it still have those images like default.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    MikDra1•7,470
    @MikDra1
    Posted about 1 year ago

    Hi, here are some tips from me:

    • Code Structure: The code is well-organized with a clear separation of concerns between HTML and CSS, which enhances readability and maintainability.
    • Design Aesthetics: The design is clean and modern, with effective use of color, typography, and spacing. It follows a minimalist approach, which works well for the purpose.
    • Accessibility: Consider adding alt attributes for images and ensuring text contrast ratios are sufficient for readability.
    • Scalability: The project could benefit from modularizing CSS for easier updates and scalability.
    • Responsiveness: Implement media queries for improved mobile and tablet views.

    Hope you find this comment helpful 💗

    Good job and keep going 😁😊😉

  • Quentin Luback•160
    @qluback
    Posted about 1 year ago

    Nice job !

    Keep focusing on CSS Flexbox as you did for the element "author", it will make your life easier !

    You can remove width and height for the element "status", it's not necessary at all to use fixed dimensions in this case for this element. I know your element "status" will take the full width available but if you apply correct CSS Flexbox rules on the element "card", you will only have to add some padding on the element "status" to render it as required in the exercise.

    Have fun !

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

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub