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

blog-preview-card

Marcus Azevedo•40
@marcusAzevedo93
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


HTML:

The HTML basically consists of a structure that includes metadata and a body with a div of class. Inside the head element, there is also the use of metatags for character and viewport configuration. There are also links to pre-connect to Google Fonts, a link to the favicon icon, and another link to the CSS style file. The page title is defined as and there is a custom grid attribute.

elements i Use

  • google fonts
  • grid
  • links
  • character and viewport configuration

CSS:

I used pseudo-selectors to select HTML elements based on their state or position relative to other elements. An example is the :hover pseudo-selector, which selects an element when the mouse is over it. In your CSS code, the :hover pseudo-selector is also used to style the link within the card header when the mouse is over it, including the yellow color.

I also used pseudo-elements to add fictitious HTML elements to the document. They are used to add content to an element without requiring an additional element in the HTML. In the CSS code, the ::before pseudo-element is used to style the fictitious element that appears before the card.

I hope this helps! Let me know if you have any more questions. 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • John Carruthers•310
    @techyjc
    Posted over 1 year ago

    Great job!

    Small suggestion maybe use the css property line-height:1.5 to space the copy text.

    Or a variant of the value.

    John Carruthers

    Marked as helpful
  • Ryan Abdaul•320
    @RyanAbdaul
    Posted over 1 year ago

    I like your design and the way you created it, keep going man, you're doing great.

    Marked as helpful
  • P
    Daniel 🛸•44,810
    @danielmrz-dev
    Posted over 1 year ago

    Boaaa Marcus!

    Deu certinho dessa vez 😁

    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

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