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

Blog review card

Bvega•40
@Bvega
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’m proud of achieving a pixel-perfect match to the Figma designs, with accurate sizing, spacing, and a crisp offset shadow. Next time, I’d streamline my workflow by automating snapshot exports and maybe explore CSS Grid for layout flexibility.

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

Variable font integration: Loading the Figtree weights via @font-face took some trial and error. I solved it by testing static fallbacks alongside the variable font in different browsers.

Box-shadow precision: Reproducing the exact 8px offset, 0px blur shadow required zooming in on Figma’s inspector and tweaking values until it matched.

Ensuring keyboard accessibility: Making the title link focus-friendly meant adding clear outline styles and testing with the Tab key. Also trying to upload the project to github pages as far as they changed the whole process and it was not very clear what the steps needed to be taken.

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

Adding a dark mode toggle driven by CSS variables

Implementing visual regression tests (e.g. with Storybook or Playwright)

Enhancing overall accessibility, such as ARIA roles or better focus management

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mahmud Kabir Usman•80
    @Miranusm
    Posted 3 months ago

    the code is okey but the learning bagde is too long

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