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

Blog Preview Card Responsive Page

jubileelin•100
@jubileelin
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I am confused on how to utilize measurements others than px for things such as font sizes and the widths of containers. I also do not know how to make the font sizes change with the dimensions of the screen as the challenge suggests so if anyone has any resources or advice on how to implement this, it would be very helpful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nigusu Daniel•50
    @KingDan123
    Posted about 1 year ago

    When it comes to utilizing measurements other than pixels (px) for font sizes and container widths, you have a few options. Here are some commonly used units: Percentage (%): This unit allows you to set sizes relative to the parent element. For example, if you set the font size of a container to 100%, it will take the font size of its parent element. Using percentages can help maintain proportionality across different screen sizes. Viewport Width (vw): This unit represents a percentage of the viewport width. For instance, setting a font size to 5vw means the font size will be 5% of the viewport width. Using vw can be useful for responsive designs as the font size will adjust automatically based on the screen size. Viewport Height (vh): Similar to vw, vh represents a percentage of the viewport height. It allows you to set sizes relative to the height of the viewport. For example, setting a container's height to 50vh means it will take up 50% of the viewport height. Em (em): The em unit is relative to the font size of the nearest parent element with a defined font size. If no parent element has a defined font size, it's relative to the browser's default font size. Using em can help create scalable designs based on the font size hierarchy. To make font sizes change with the dimensions of the screen, you can use CSS media queries. Media queries allow you to apply different styles based on the characteristics of the user's device, such as screen width. By defining different font sizes for different screen sizes, you can achieve responsive typography.

    Here's an example of using a media query to change font sizes:

    css Copy .container { font-size: 16px; }

    @media screen and (max-width: 768px) { .container { font-size: 12px; } } In this example, the font size of the .container class is set to 16 pixels by default. However, when the screen width is 768 pixels or less, the font size is changed to 12 pixels. Remember that implementing responsive design requires testing on various devices and screen sizes to ensure your website or application looks and functions well across different platforms.

    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