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

3-Colum-Preview-Layout : PURE HTML | CSS | WITH A PINCH OF ANIMATIONS

karenefereyan•375
@karenefereyan
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


Hi everyone!

This was another great challenge. Here are my major takeaways:

  1. How does one determine when and where to use <a></a> or <button></button> I think I am convinced now that links should be used when clicking on them simply navigates the user to a different section either on the same page or elsewhere. A button should be used instead, when clicking on it will trigger an action that can change the functionality of the frontend or backend of the website, such as when a new account is to be created. I also think that the other situations in which a button should be used are: in a form where the type attribute can determine the default event of the form, or if clicking on the button has no functionality except when triggered by Javascript. My convictions are based on these articles I read:

https://css-tricks.com/a-complete-guide-to-links-and-buttons/

https://uxmovement.com/buttons/when-to-use-a-button-or-link/

  1. Debugging is a superpower. I couldn't agree more. I coded this site for desktop first and then added media queries for smaller screens. I realized after tackling the responsiveness that the cards stacked up on each other on desktop screens. That was weird, cause bear in mind, i had successfully coded the desktop screen to stay side by side. Guess what I found? I eventually realized that I had written a media query to target devices with a max-width of 7680px instead of 768px. Hilarious now 🤣🤣🤣🤣🤣🤣🤣🤣🤣. It wasn't when I was in the process of debugging.

  2. I also tried to make better use of pseudo-classes and elements.

  3. What do you think of my animations and the hover effect? Did I do well?

Feedback is very much appreciated.

As always, keep coding! Happy coding!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on karenefereyan's solution.

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.