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

Blog Preview Card using HTML, CSS and some pseudo class

Peepytoo•110
@Peepytoo
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?

figuring out the structuring was quite difficult, but I'm quite content with the result (other than the fact that it lacks semantic HTML5 code). I also think that my utilization of flexbox turned out pretty well at the end.

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

Structuring was the main challenge, and organizing the elements so that they can be properly individually formatted.

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

The formatting of my code and if it's easy to read. I didn't really use semantic HTML5 code since it kept messing up my format so I'm not really sure how my readable my code actually is.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chamu•13,860
    @ChamuMutezva
    Posted 3 months ago

    Hi Peepytoo

    You have done well so far, here are some areas that you can have a look at:

    1. A website should be made up of elements such as landmark elements which are important for the structural organization of a webpage. One such landmark element is the main element which is responsible for the primary content of a webpage. The div with the id=div1 can be your main element and the other with the id=attribution can be the footer element
    2. use semantic elements, a div is a generic container that has no meaning for accessibility purporses. For example <div id="publish">Published 21 Dec 2023</div> - this could have been a p element as well as the <div id="box2">Learning</div>
    3. alt values are important in an img. If the img is decorative the value should be empty as in alt="" but in all other cases the value should represent the message that is carried in the image.
    4. check for a modern reset stylesheet, it is important to normalise your styles so that you can have a site that looks the same on different browsers. I normally use one by Andy Bell.
    5. One such declaration that you can find in a reset stylesheet is where the body has min-height: 100vh. I see that you used height: 100vh - which has its own limitation if you have a lot of content . The min-height: 100vh allows the content to scale up to exceed the 100vh
    6. Use class for styles , using id is not what I would recommend as the id has a higher specificity.
    7. avoid explicit sizes on container elements , such as in the div1 . Instead of width: 384px which keeps the size fixed at 384px you can utilise max-width - that allows your container to grow up to a certain size (good for responsive design) and also using px is not the best option , use rem in most cases. The following article will explain some of the reasons Why you shouldn't use pixels for font-size. The height also should be ommited - the contents of the container should decide the height to avoid overflows as most of the time you won't know the size of the content or device that will be used.
    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 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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub