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

Blog preview card

IO•710
@i000o
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?

This one took me less time than the first. I tried to keep the problems as simple as possible. I'm satisfied with the end result.

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

I had a hard time figuring out how to order the items in the stack like the images and different text elements on the card.

I tried to use the order: property but I realised that since I had set body to display: flex;, the section element I used for the card was the flex-item, not the elements within.

When I tried to make a flex container within another by assigning display: flex to section (the card), the problem seemed to become more complicated. So, I just did the simple thing and ordered them the way they appear in the HTML, which wasn't my preference.

How best to address this when ordering flex items in a container?

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

Please advise as to the above. I don't imagine that the best way was to reorder the stack in the HTML, but I couldn't figure out how to make proper use of the order property within flex containers. In a situation like this, would you always assign the flex container to body rather than the card itself? I'm not sure...

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Camryn Tidsworth•130
    @CamrynTidsworth
    Posted 7 months ago

    Great design, looks very close to the original! The code is well-written and easy to read.

    I think if you add "display: flex;" to the section element you can then use order on the content inside. I've never done it before so let me know if it does/doesn't work. Out of curiosity, why do you want to have things ordered differently in the HTML? Is it because you want the more relevant headings to get more SEO attention?

    One other tip I learned doing this design was how to add hover states to elements. In this instance, to make the title turn yellow and turn the cursor into a pointer you can add this to your existing CSS:

    h2:hover { color: yellow; cursor: pointer; }

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub