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

four card section html css beginner solution

Viola Clara Citra P•20
@violaClara
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I made the 4 card section with css-position property is it ok to do that? How do that with float or flex?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • darryncodes•6,350
    @darryncodes
    Posted over 3 years ago

    Hi Viola,

    I agree with argel. For learning yes for responsiveness no.

    Here are some really helpful resources that you might learn from:

    • A Complete Guide to Grid
    • A Complete Guide to Flexbox
    • Scrimba - learn FlexBox for free
    • Scrimba - learn Grid for free
  • argel omnes•1,780
    @argelomnes
    Posted over 3 years ago

    Hey Viola,

    For learning purposes, yes. For client work, no. My suggestion is to use grid. Second best choice is flexbox. You can also combine these two.

    I also recommend organizing your files. Like grouping svgs inside an 'image' folder and a 'font(s)' folder for font(s). Speaking of fonts, you haven't linked yours yet. You can directly link it from here. Choose only the styles you need and it will generate the link ready for use. Note: You won't need the font file/folder anymore if you do this.

    You also missed the mobile layout. Google recently launched Learn Responsive Design. Some sections are still in the works but you should definitely bookmark it. Frontend Mentor also has a resource section if you want to explore more.

    Cheers!

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