Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

css and HTML

MHIEN•230
@MinHien-git
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have problem when use display grid :column card1 lost and I have to use margin for it I need solution for it

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grishmita•105
    @Grishmita
    Posted almost 4 years ago

    hie,

    1. I think when you use the overflow hidden thats the time you should think some thing is wrong. 2)And there is now need of flex or grid inside the card cause thee is only h1 paragraph and button so i dont think it has any meaning .just use margin to element for positioning it and padding for how much we should stuff the element from all the side to look a certain way .

    Sometimes you need start simple so just start simple see if that not working and then move further and please clear any one concept css grid or flexbox and use any one to make project in which u feel confident watch on youtube how to make responsive flex box card take reference from there . hope this one is helpfull for you . I myself , I'm a slow learner so if i can do it u can also too . So keep slow but improve the quality of your knowledge that you have and then move forward .

    Take one step at a time :)

  • Carl Pericles•400
    @CarlPericles18
    Posted almost 4 years ago

    Hey, nice work on this project, I would recommend using :hover on your "learn more buttons" it would make it a bit more active, also you can reduce some of the paddings I see in between the button and the statements. Overall it looks responsive and good. Also, I try accessing your GitHub, it said it wasn't found, you might've misspelled something.

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