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

Article Preview Component

accessibility, sass/scss
Neil Kanakia•300
@neilk17
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


📍Things that were difficult:

  • Getting a downward triangle below the share button: Not sure what the best approach is to achieving this.
  • Getting a smooth transition to a responsive design: Was not able to create the right sizing in the mobile version of the site.

Would love to hear any feedback 😀

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Md5 dalton•1,430
    @md5dalton
    Posted almost 3 years ago

    Hello Neil 👋

    To center the card perfect in the page use flex box:

    body {
      display: flex;
      align-items: center;
      justify-content: center;
      flex-direction: column;
      min-height: 100vh;
      /* padding-top: 20rem; */
    }
    

    If you want to make your site responsive, I'd suggest you to go with mobile first approach which means all default styles are for mobile and then define media queries for bigger screen devices. I'll demonstrate:

    .article-container {
       min-width: 300px;
       max-width: 730px;
    }
    
    /* Large Devices */
    @madia (min-width: 768px) {
        .article-container {
           display: flex;
           align-items: center;
        }
    }
    

    This way you only have to define the flex box for larger screen devices. Also add some side padding on body to make sure the card doesn't flush against viewport edges. padding: 0 1rem; as an example. 👌

  • Abdalla Rahmah•260
    @AbdallaRahmah
    Posted almost 3 years ago

    nice work Nell, i like your work and i have some ideas for you:

    • instead of adding a large padding to the body element you can add min-height: 100vh and justify content: center this will help you center the main element.

    • also you can remove the article-container div and duplicate its styles to the main tag.

    best of luck for you.

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