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

flexbox,css,html newbie

uzumakiabba•80
@recklessboss
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 am new to css and html ..so please take a look at this and see what you think about it and the areas i should improve,Thank you :)

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jiro Ricaro•715
    @jiroRi
    Posted about 5 years ago

    Hi @uzumakiabba! You have a great solution considering that you are very new to css and html! 🤩💯

    I have a few suggestions that may be able to help you:

    • Use the neutral | dark color provided in the style-guide.md for your .heading-sub and your h3 elements.

    • You should dive deeper in Flexbox and learn more about it. It will definitely improve your current solution.

    • With regards to flexbox, try adding a property of it: align-items: center to your .container div, you will already see a huge improvement after doing so.

    Now to expound on what made such a nice change.. by adding the display: flex; property, you will have a property of flex-direction: row; by default(even if you didn't explicitly type it). This means that your main-axis goes horizontally and your cross-axis will go vertically. What align-items: center; does is it aligns the flex items on the cross-axis.

    So, going by your solution, it should center your flex items vertically. Btw, center is one of the property values of align-items and there are more you should look into.

    There are a lot of great things to learn in Flexbox and you should definitely check the Resources Page to dive deeper.

    But overall, you really did a great job!

    Good luck and Keep at it! 💪 - Jiro

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