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

Responsive 3 Column Card Component (No Media Queries)

accessibility, bem, lighthouse
Vanza Setia•27,715
@vanzasetia
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


Hello Everyone! 👋

I manage to make this website responsive without media queries. Feel free to take a look!

Of course, any feedback is appreciated!

That's it! Happy coding everyone!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Smita•375
    @Smita-14
    Posted almost 4 years ago

    It's surprising to know that you coded this on a phone so well!✨✨ It is brilliantly done! 👏👏

    Marked as helpful
  • bunee•2,020
    @buneeIsSlo
    Posted about 4 years ago

    @Vanza, Perfect! as usual.

  • Shashree Samuel•8,860
    @shashreesamuel
    Posted almost 3 years ago

    That is quite commendable that you coded from a mobile device. Keep up the awesome work and great job using the ch css unit

  • P
    j5•2,270
    @jmnyarega
    Posted about 4 years ago

    Impressive 👏

  • Account deletedPosted about 4 years ago

    Hello vanzasetia, 👋

    Congratulations on completing this challenge.

    Your solution looks good and responsive also.

    Coding on phone 📱 is very hard Hats off ! for that

    One question I have (how do you manage to make it responsive on all viewports)

    Great work by the way.😊

  • P
    Patrick•14,265
    @palgramming
    Posted about 4 years ago

    Yes it looks great and coding it on a phone is so impressive 🌟🌟🌟🌟🌟

  • Dinesh•1,115
    @Dinesh1042
    Posted about 4 years ago

    Great work on this challenge. You have managed the responsiveness of the site very well that's cool. Keep up the great work!

  • JJ•25
    @j-j-martin
    Posted about 4 years ago

    Haha you're a legend! "No excuses" is your guiding principle I guess, 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

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

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

Oops! 😬

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

Log in with GitHub