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

Responsive Article Preview using HTML, CSS and JavaScript

P
Petter Torst Saatvedt•180
@PetterTSaatvedt
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?

Overall I feel very comfortable with the implementation of responsive design and styling in general, and it was great practice to combine this with some basic javascript. Next time, I will do some more research beforehand, to avoid having to change my approach mid-project as I did this time, due to finding the toggle class option in javascript.

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

The main challenge for this project was definitely finding a solution for how to handle the changes in design and layout when clicking the share button. Not only should it adapt in terms of screen size and state, but also for resizing of the window, as this could result in a bugged layout. I ended up using the toggle method for the classList property, which allowed me to toggle classes on and off according to specific scenarios.

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

All feedback is welcome, as I'm always looking to learn. Perhaps there is a more efficient way to handle the toggling?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hi @PetterTSaatvedt!

    The developed solution looks great!
    Suggestions for Improvement:


    1) Fixing the Image Cropping Behavior

    For the "drawers" image on desktop resolution, object-fit: cover ensures the image maintains its aspect ratio while fitting into the available width. However, it crops the image equally from both sides (left & right).

    In the design reference, the image is only cropped from the right side, not the left.

    You can fix this by adding object-position: left, which ensures cropping happens only from the right side:

    This small detail enhances pixel perfection!

    2) Missing Triangle Below Social Share Box

    On desktop resolution, the social share icon box (#share) is missing the small triangle below it.

    You can create this triangle using CSS borders:

    #share:before {
        content: "";
        position: absolute;
        width: 0;
        height: 0;
        border-left: 10px solid transparent;
        border-right: 10px solid transparent;
        border-top: 10px solid var(--very-dark-grayish-blue);
        top: 100%; /* Aligns at bottom */
        left: 50%; /* Center align */
        transform: translateX(-50%); /* Center align */
    }
    

    This creates a perfect downward-pointing triangle!

    🔗 For more details, check out this CSS-Tricks article:
    👉 CSS Triangle Trick


    Everything else looks fantastic! Keep up the great work! 🚀

    Marked as helpful
  • David Mwalimu•260
    @broken555wheel
    Posted 4 months ago

    Amazing solution, Petter.

    I'm also hoping to see/learn a more efficient way to handle the toggling. I see you used classList while I directly manipulated CSS. Is it more advantageous to use your approach?

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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