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

Static Blog webpage with HTML and CSS

Jose Arturo Soraiz-Muniz•60
@jasm32
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?

Proud that I have learned how to use vectors for first time. Next time, I will try to play around with them to understand it better.

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

Was confusing how to make the blog image using from rectangles, vectors, and frames.

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

I would like suggestion and tips on how to make the code inside the blog-image frame more organized and clean.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Ricky Dodd•40
    @rickydodd
    Posted 5 months ago

    What you did well:

    • The solution looks very similar to the design, visually.

    What could be improved:

    • Remove the padding from the page-background class.

    When the viewport is short, there is a large gap at the top that does not respond well.

    The following

    .page-background {
      display: flex;
      width: 100%;
      min-height: 100vh;
      padding: 251px 0; /* remove */
      justify-content: center;
      align-items: center;
      background-color: #f4d04e;
    }
    

    becomes

    .page-background {
      display: flex;
      width: 100%;
      min-height: 100vh;
      justify-content: center;
      align-items: center;
      background-color: #f4d04e;
    }
    

    Because the display: flex declaration makes the element a flex container, which is a block-level element, you can also remove the width: 100% declaration. The declaration is redundant, as block-level elements will naturally fill the width.

    • Use semantic HTML.

    As it is a card, I suggest using the article element to represent the card. The rationale is that cards are self-contained compositions that can be re-used inside a HTML document, so article is an excellent choice.

    • Extract and optimize the SVG.

    In terms of the SVG itself, the only recommendation I have is to copy the SVG markup and use a tool like SVGOMG to extract it from the markup and make it into an SVG file, then use that in the HTML.

    Something like SVGOMG will also flatten and optimize the SVG. Hope you find this helpful.

  • Akiza•30
    @NagatsuAkiza
    Posted 5 months ago
    1. yes
    2. yes
    3. yes
    4. yes
    5. yes

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