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

Blog Preview Card

Chris•110
@cgyeager
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?

Think I got close.

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

Was trying to align image to the center without all the text being centered, fixed by using div wrapper.

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

Anything that needs improvement.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted about 1 year ago

    Excellent work! 👏

    Here are some suggestions:

    • Use semantic tags. The ´card´ can be an article or section.
    • In published ... for the date you can use the time tag.
    • The avatar class makes sense as a div.
    • When you use article or section it is mandatory that it has a h? tag inside. You must remember that headings are consecutive.
    • Your CSS variables should be more declarative; for example, w1 is just 2 letters that don't tell me anything; however fw-500, makes some sense: font-weight: 500.
    • The width of the card you are declaring with vh, you should try vw. I recommend you to check clamp, it can help you with the size of the card as well as the ‘font-sizes’.

    I invite you to check my solution, you may find some ideas.

    Happy coding! 😎

    Marked as helpful
  • Deivisson Lisboa•190
    @DeivissonLisboa
    Posted about 1 year ago

    Hey, nice project. Well done.

    I suggest that you be more general with your CSS, so it becomes more scalable. Imagine this component as part of a larger site, where other CSS styles are affecting it. You should set the stage on the body or a higher-level parent to fully leverage the cascading nature of CSS.

    Also, Images don't behave well as flex elements. When dealing with this situation, you should wrap them in a div. This will make it easier to center them and set the width of the image.

    One feature that you didn't include in your project was the hover state. Note that this component is intended to lead the user to another blog page, so the <h1> should have an <a> tag. This will change the cursor to a pointer and allow you to redirect the user to the other page. Styling the hover state is as simple as:

    h1 a:hover {
        color: var(--yellow);
    }
    

    I hope you find value in theses tip.

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
Frontend Mentor logo

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