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

Blog preview card

wxyzz22•240
@wxyzz22
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 gained a lot more experience working with flexbox. I think next time I will be able to consult external resources less when I am writing code.

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

I was having trouble using flexbox to align the items. So I paused the project and read more on CSS introductory guides for flexbox.

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

Welcome any suggestions on more natural CSS styling pattern/template.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    M Kerr•2,130
    @mkerr-github
    Posted 3 months ago

    "Welcome any suggestions on more natural CSS styling pattern/template."

    ✅ Good Things:

    Clean use of Flexbox for layout.

    Consistent spacing and card styling.

    Custom fonts clearly applied.

    🔧 Key Suggestions:

    Font Management: Avoid separate font-family names like "Figtree-ExtraBold" and "Figtree-Medium". Use a single font-family ("Figtree") and control weight with font-weight: 800 or 500.

    Use CSS Variables: Declare colours (like rgb(244, 208, 78), grey, black) as variables under :root for consistency and easier updates.

    Reduce Redundancy: Instead of repeating styles across h1, h2, p, group shared properties (like line-height, letter-spacing) in a base typography class or apply them to body.

    Box-sizing Best Practice: Apply box-sizing: border-box; globally via:

    *, *::before, *::after {
      box-sizing: border-box;
    }
    

    If you found anything in this comment helpful, please remember to click the "mark as helpful" button. Thank you!

    Keep up the good work, and keep going! 👋

    Marked as helpful
  • linus-21•50
    @linus-21
    Posted 3 months ago

    its good

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