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

Blog Preview Card with HTML and CSS

P
ImposterCodeVault•90
@ImposterCodeVault
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?

Last time I didn't look at the figma files, this time around I looked at them from the start to try and get the solution as close as possible to the proposed design.

What specific areas of your project would you like help with?
  • When trying to get the text content to fit properly in the card-content section, I had issues with the tag having a default margin. Am I supposed to remove this margin in order to get things to size correctly? Did I do this the right way by specifying 0 margin on all elements at the top of my css?

  • What are some better practices I could have followed with my CSS?

  • I tried to follow the design from figma as much as possible, but this resulted in a lot of pixel values being specified, which I don't think is great for resizing and responsive layout. What could I have done better here?

  • The challenge says: The font sizes in this project are slightly smaller in the mobile layout. Find a way to reduce font size for smaller screens without using media queries. I'd be keen to see how other people approached this. I know I could use vw units for the font size, but I don't know how to set the starting font size using pixels and then scale from there.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Diego Ramírez•880
    @Diego2Drm
    Posted 8 months ago
    <p class="text text-medium text-gray"></p>

    Why put more than one class on the tag?

    .text-small { font-size: 14px; }

    .text-medium { font-size: 16px; }

    .text-large { font-size: 24px; } you can use variables..

    For example:

    :root{ --text-large: 30px; }

    h1{ font-size: var(--text-large); }

    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

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