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

css flexbox

promise•520
@ugochukwuuu
A solution to the Fylo data storage component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


for some strange reason i struggled with making the card centered on the page, so I would very much appreciate it if someone could help me with that

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aya Saeed•1,020
    @Aya-Saeed261
    Posted about 3 years ago

    Hello, @practitionerofsorts! :) congratulations on finishing the challenge! Now to fix the centering issue, wrap the card and the attribution div in a main tag and use flex box :

    <main>
      <card></card>
      <div class="attribution"></div>
    </main
    
    body{
    display: flex;
    justify-content: center;
    align-items:center;
    }
    

    and to perfectly center the card delete those styles from the card class

    transform: translateY(4em);
    margin-top: 3em;
    

    this will hopefully fix the centering issue and also the landmark accessibility issue by wrapping the whole thing in a main tag, then generate a new report.

  • Udeh Ifeanyi•520
    @Ifescohub
    Posted about 3 years ago

    Very great work you have done here. It looked closely like the design. Here are my observations regarding your challenge. (I'm also learning though).

    Try to add the following to your body in the CSS in order to center it well: height: 100vh; display: grid; place-items: center;

    -And also regarding your report, try to place your main card class in "main" rather than "div". Like:

    <main class="card"> You can place other divs inside this </main>

    -And lastly, your attribution class should be in a "footer" tag and not "div" tag. I believe this will help to solve the report issues. Happy coding.

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

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