Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

My Blog Preview Card Solution

P
Jocelyne Teles•180
@JocelyneTeles98
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?

This time I did almost everything by my own. I only had to research a little bit about hover state in CSS.

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

The most challenging part for me this time was the box-shadow. Since the free Figma version doesn't support dev mode anymore I had to "translate" the shadow aspect into code. But at the end it wasn't that difficult.

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

I would like to receive suggestions about sizing and positioning for responsiveness. I think I managed it well but I would like to learn about the best practices or the easiest way to think about it when I have to code that part.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Brian•150
    @briangesteban
    Posted 9 months ago

    Hi Jocelyne,

    It seems you've got sizing and positioning right. You've just missed a CSS default reset. As you can see, even when you already set your max-width for the blog-card, it still doesn't grow to your desired width limit since the box-sizing property of the element is set to default, which is content-box.

    The blog-card width on desktop is growing up to 456px because if you do the manual calculation in box-sizing: content-box it will add the margins + paddings + border + content size. It goes like this, Your margin is 12px on both sides, padding is 24px on both sides, and 384px for your content size, in total it would go up to 456px (12px + 24px + 384px + 24px + 12px = 456px).

    To fix this and get an accurate sizing. You'll have to change the default of box-sizing property to border-box.

    You could set it for all elements like this: (the * selector selects all elements, and change the default box-sizing for all elements)

    CSS Snippet: * { box-sizing: border-box; }

    References:

    • CSS Box Model
    • Box-Sizing Property

    P.S. You've missed the border of the blog-card and you could also reset the margins default to 0, right now it seems that you have a margin on the body element that you didn't set. You could also use the * selector for this.

    Hope this helps you. Happy Coding!

    Marked as helpful
  • P
    Steven Stroud•11,890
    @Stroudy
    Posted 9 months ago

    Exceptional work! You’re showing great skill here. I’ve got a couple of minor suggestions that could make this stand out even more…

    • You have wrapped loads of HTML elements in <div> that dont need to be, The element inside already has semantic meaning and it is on its own, Making the div irrelevant,
            <div class="content-label">
              <p>Learning</p>
            </div>❌
            <div class="content-date">
              <p>Published 21 Dec 2023</p>
            </div>❌
    
    • Using a full modern CSS reset is beneficial because it removes default browser styling, creating a consistent starting point for your design across all browsers. It helps avoid unexpected layout issues and makes your styles more predictable, ensuring a uniform appearance on different devices and platforms, check out this site for a Full modern reset

    • I think you can benefit from using a naming convention like BEM (Block, Element, Modifier) is beneficial because it makes your CSS more organized, readable, and easier to maintain. BEM helps you clearly understand the purpose of each class, avoid naming conflicts, and create reusable components, leading to a more scalable codebase. For more details BEM,

    • While px is useful for precise, fixed sizing, such as border-width, border-radius, inline-padding, and <img> sizes, it has limitations. Pixels don't scale well with user settings or adapt to different devices, which can negatively impact accessibility and responsiveness. For example, using px for font sizes can make text harder to read on some screens, Check this article why font-size must NEVER be in pixels. In contrast, relative units like rem and adjust based on the user’s preferences and device settings, making your design more flexible and accessible. Use px where exact sizing is needed, but prefer relative units for scalable layouts. If you want a deeper explanation watch this video by Kevin Powell CSS em and rem explained. Another great resource I found useful is this px to rem converter based on the default font-size of 16 pixel.

    • Line height is usually unitless to scale proportionally with the font size, keeping text readable across different devices. Best practice is to use a unitless value like 1.5 for flexibility. Avoid using fixed units like px or %, as they don't adapt well to changes in font size or layout.

    I hope you’re finding this guidance useful! Keep refining your skills and tackling new challenges with confidence. You’re making great progress—stay motivated and keep coding with enthusiasm! 💻

    Marked as helpful

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