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

Used inline block and div

Luciel V.•100
@vanderloop
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 most proud of how i figured out how to get the 'learning' to not spread across the whole row. next time, i'd try not to think as hard about how to center the div, because that messed me up a few times.

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

centering the div, so i looked up how to center the div online. also, how to get the yellow 'learning' part to only be around the word and not the whole line, so i played around with it in vscode.

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

the avatar and text, and just overall constructive criticism.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan Heslop•2,440
    @dylan-dot-c
    Posted 9 months ago

    Well done! This is a good solution but there are a few ways you can improve.

    • make use of semantic HTML tags like main and article this can help screen readers and replace the divs you have
    • I think you have overused the heading elements and they could be used better. I think there should be only one heading tag here and that would be the title, HTML&CSS... and it can be an h2 as it doesn't need to be an h1. The rest of the tet could be paragraphs.

    Also for the avatar, you could use flexbox to get it aligned vertically and look good. You might also need to put it into a separate container.

    Also make use of css variables in your code especially for the colors

    Overall you did a great job so take care and all the best

  • Franklin Nmaju•110
    @Gentlefrank
    Posted 9 months ago

    Nice job

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

Pinellas Technical College

Web Development Program at Pinellas Technical College in Clearwater, FL.

Learn more

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