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

3 column card component (html, css)

Jakub•210
@flexer89
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


Could you tell me if i have a tidy code? Or maybe there is some things to improve in code organisation. I also want to as if i correctly uploaded repository. I am waiting for some extra tips

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nene16•95
    @Nene16
    Posted about 4 years ago

    About your repository, I had the same problem. I solved the issue changing alt="" with title="".

    Marked as helpful
  • P
    Heather Smith•240
    @sorengrey
    Posted about 4 years ago

    About your repo -- I don't think it's necessary to include the style guide or the readme template. Those are just guides for you. You can add them to your .gitignore to keep them from being pushed to your repo.

    As for your code, you can round the edges of your divs in CSS with the border-radius property. When I did this project, I used border-radius: 0.5em.

    Otherwise, this is looking great!

    Marked as helpful
  • Андрій Рогов•1,155
    @Andrii-Rohov
    Posted about 4 years ago

    Try to use gitHub pages, its in repository settings, you would only need to add index.md file into youre project and write all files wich needed for page like this (index.html style.css etc)

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