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

Blog Card

P
Rodrigo•250
@RiickyRiick
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 feel way more accomplished since I completed this project with only searching how to use the overflow: hidden CSS rule. Other than that, I completed it all by myself.

What I would do differently is to continue coding and not put all my attention into one section. I didn't necessarily get stuck in anything, but I did, however, keep trying to perfect the sizing. I was very adamant about the font-sizing problem. I should have just come back to it and continued at a later time.

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

Getting a responsive response from the font-sizing was my biggest problem with this project. I did end up using media queries to fix the sizing for the mobile design.

How do you fix the font-sizing without using media queries? With vw, em, rem, px, or any other unit?

Also, my sizing for my card-container ended up pushing the .attribution class down, creating a scrollbar. I ended up just putting an overflow: hidden within the body to remove the scrollbar. Then, I inputted position: relative, adn a bottom within the .attribution class to bring it back up for visibility.

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

I need help with responsive font-sizing, how to utilize it more effectively, and how to better adjust the sizing so I don't need to use the overflow CSS rule. All the help is very much appreciated, thanks again!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Rodrigo's solution.

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.