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

This a project on blog template contain CSS info. HTML & CSS

Chandra Vamshi•20
@imchandravamshi
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 am proud that my project and preview looks similar and I wanted do on the JavaScript.

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

The project is pretty simple for me that I practiced HTML and CSS a long time ago and I'm about to complete JavaScript.

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

I think I am not pro at flexbox and grid layout so I think I should work on that.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    M Kerr•2,130
    @mkerr-github
    Posted 2 months ago

    Looks good, well done!

    Flexbox is a layout tool that can help with responsive design, but it isn't responsive design.

    Flexbox lets you control alignment and spacing inside a container. It's ideal when dealing with one row or column of items in a container. Those items could be anything from images to text boxes.

    Grid is similar to Flexbox, but allows you to set out the items in a grid consisting of both columns and rows.

    Here's some useful primer articles from W3 schools that will explain the basic principles of each, and where you can try them out with the code :

    Flexbox:

    https://www.w3schools.com/css/css3_flexbox.asp

    Grid:

    https://www.w3schools.com/css/css_grid.asp

    Responsive Design

    Please remember to click the "Mark as helpful" button, thank you!

    Keep up the good work, and keep going! 👋

  • bloo2kk•50
    @bloo2kk
    Posted 2 months ago

    I really like how you brought this project to life — the layout is clean, the colors are well balanced, and everything feels intentional.

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.

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