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

Css customization, HTML, Bootstrap Grids and Bootstrap container

bootstrap
vinay kandoi•120
@vinaximus
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 couldn't get the rounded corners perfectly. Am I doing the whole thing in a wrong way? In my mobile, the cards are not aligned to the center.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rio Cantre•9,650
    @RioCantre
    Posted over 3 years ago

    Hello there! Good job in completing this project. Looking at your solution, I would suggest the following for you...

    • Remove the border radius in the .container-card rule set. Add border-top-left-radius: 10px; and border-bottom-left-radius: 10px; in .card-orange and .card-green with border-top-right-radius: 10px; and border-bottom-right-radius: 10px;
    • Include media queries for the responsive design and adjust the borders into border-top-left-radius: 10px; and border-top-right-radius: 10px; in .card-orange and .card-green with border-bottom-left-radius: 10px; and border-bottom-right-radius: 10px;
    • Wrap the container with specific tag like main for readability
    • Uncomment the attribution wrap it with footer tag, add your name and links to your work/portfolio.

    Overall you did good and Hope this is helpful!

    Marked as helpful
  • Travolgi 🍕•31,300
    @denielden
    Posted over 3 years ago

    Hi Vinay, great work! For fix the corners fix the border-radius property to container-card. class. You can use firstchild and lastchild

    .container-card:first-child {
       border-radius: .5rem 0 0 .5rem 
    }
    .container-card:last-child {
       border-radius: 0 .5rem .5rem 0
    }
    

    Try to align content with flexbox and removing al margin from row and container class.

    Wrap the content page into main tag for improvide accessibility

    Also try to adding a little transition on the button with hover effect ;)

    Hope this help ;) And keep it up!

    Marked as helpful
  • vinay kandoi•120
    @vinaximus
    Posted over 3 years ago

    Thanks a lot, didn't know about media queries, will research

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, SASS, 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

Oops! 😬

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

Log in with GitHub