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

Article Preview Component using basic HTML, CSS & JS

BozJR•260
@BozJR
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Im most of proud of being able to complete this but it was difficult in terms of figuring out the JS and then putting my thoughts onto the code. got there in the end with some help.

What challenges did you encounter, and how did you overcome them?

using the JS and getting it to do what i wanted.

What specific areas of your project would you like help with?

Just need more practical PRACTISE with JS.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jay Khatri•4,230
    @khatri2002
    Posted 5 months ago

    Hi! The developed solution looks great and satisfies the requirements for both desktop and mobile resolutions! Just a few UI suggestions to bring it closer to the design reference:

    1. Center Align the Card

    To center align the card properly without relying on margins, apply the following styles to the <main> element:

    min-height: 100vh;  
    display: flex;  
    align-items: center;  
    justify-content: center;  
    

    This approach eliminates the need for any fixed margins, ensuring consistent centering across different screen sizes.

    2. Fix the Stretched Image Issue

    If you notice the drawers image in the given design reference for the desktop resolution, it is maintaining its aspect ratio while being cropped only on the right side, not equally on both sides. However, in the current solution, the image seems stretched due to fixed height and width.

    Steps to Fix:

    • Add the following property to ensure the image maintains its aspect ratio:

      object-fit: cover;  
      

      This ensures the image adjusts to the provided dimensions while keeping its aspect ratio intact.

    • To crop the image only from the right side (as seen in the design reference), add:

      object-position: left;  
      

      This shifts the focal point of the image to the left, ensuring the cropping happens primarily on the right side.


    Why These Adjustments Matter

    These minor adjustments align the design more closely with the provided reference. Observing such details train your eye for pixel-perfect design, which is a valuable skill.

    Keep up the great work! You're doing an excellent job! 🚀

    Marked as helpful
  • Mohamed Ragheb•560
    @mohamed-fm
    Posted 5 months ago

    Great code! However, you might want to avoid giving the article__content-container a height property. This will allow it to adjust automatically for smaller screen sizes and will help resolve the issue with the mobile-social-sharing-bar, making it stick to the bottom.

    Additionally, you can use overflow-x: hidden; on the body and correctly position the share-shape-container to prevent any overflow. Overall, it's excellent code!

    Marked as helpful

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, SASS, 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