Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Four card feature section

LiamHilton•20
@LiamHilton
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I worked on my HTML and CSS through prior knowledge before utilising a tutorial by Kevin Powell as i continue to explore different practices from professionals in the field. my process has been to figure out what it is i want to create. What i will use being Flexbox or Grid then working systematically within the html so that i can form my CSS.

  • A key thing with this template was " Cascading order in my html" -- This meant also looking at the mobile version and thinking about how the layout will form once no longer in desktop. This worked nicely with Grid but i also explored my options with Flexbox. -- I am building a solid foundation for CSS through FrontEnd Mentors tasks and although im currently learning JavaScript im finding it refreshing to come back and tinker with these tasks. It is giving me an added daily drive to challenge myself again and stay consistent with my FrontEnd Web Development path.

-- furthermore i added a slight variation that was not in the task but i enjoy adding to my cards.This was a :hover class which changed each cards box shadow to a lighter gradient of the initial border-top. If you haven't tried it yet then this could be great to play around with and bring a slight dynamic to the simplicity of the task. See code below:

.border-teal { border-color: var(--clr-primary-teal); } .border-red { border-color: var(--clr-primary-red); } .border-yellow { border-color: var(--clr-primary-yellow); } .border-blue { border-color: var(--clr-primary-blue); }

.border-teal:hover{ box-shadow: 0 1rem 1rem -.5rem hsl(180, 29%, 30%); } .border-red:hover{ box-shadow: 0 1rem 1rem -.5rem hsl(0, 38%, 38%); } .border-yellow:hover{ box-shadow: 0 1rem 1rem -.5rem hsl(34, 53%, 48%); } .border-blue:hover{ box-shadow: 0 1rem 1rem -.5rem hsl(212, 39%, 40%); }

What challenges did you encounter, and how did you overcome them?

i encountered a few challenges when playing around with grid and Flexbox but found GRID to provide the best output for this template. I sourced out a tutorial from Kevin Powell which also brought me great enlightenment on individual aspects i hadn't learnt before in CSS. I have been working on looking at how a page looks so i can then visualise how i will portray my code to get the correct results.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on LiamHilton'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.