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

3 Col Preview Card using Bootstrap

Sebastien•55
@SebastienPJ
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 was mainly focused on responsiveness here. Happy with the way it turned out. Any feedback is welcomed. Things I need to work on: Layout (margins, paddings, displays), Readability, Modularity. I will redo all challenges as my abilities improve.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted about 4 years ago

    Hey, great work on this one. Layout in desktop is somewhat narrow but is fine for now, the mobile state however is too narrow.

    Suggestions would be that:

    1. On your hover properties on the bottom. Instead of specifying every properties like border-width, border-size. You could border only. Like this border: 1px solid red. This will really help you on the long run and prevent massive codes especially when there are lots of hover state.

    2. It will be really awesome of instead using % in your margins, use other units like rem. Because % is scaling right, so a user with different screen dimension differs what they see. Sometimes it can be really awesome but sometimes it is not. So it is good to use rem , that won't scale with the screen. As well as for the paddings, do not use %, or you can use it as long the parents dimension is specified and can be controlled.

    3. Making the width of your button much large will be great. Right now the text inside the buttons are wrapped in another row, which creates this huge button right. So adjusting the width so that it will capture the text in one line.

    4. Lastly, the mobile state, adjusting those margins will be really awesome so that it won't look like that it is squished or narrowed.

    If you need more help, just drop it here okay and i'll be gladly to help you with it. Overall, great job^

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