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

Responsive Article preview, using flexbox and JS

accessibility, sass/scss
Williams Akanni•350
@shadowbanks
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?

I spent a lot of time trying to get the active part, this was also my first time doing something like that.

I'm proud of myself for seeing it through to the end.

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

I would like to know if how I handled the active part is fine and if there's a better approach particularly the js part.

Thank you for your time :))

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hi! The developed solution looks really good! Below are my UI suggestions:

    1. Use of Button Instead of Div

      • Currently, you're wrapping the share-icon image in a <div> and handling the click event on the image itself.
      • Since this element performs an action on click, a <button> element would be more appropriate.
      • Why?
        • Accessibility: Buttons are natively focusable and actionable, making them more accessible for users with assistive technologies.
        • Semantics: Buttons inherently signify interactivity, improving the semantic structure of the code.
    2. Creating a Perfect Circle for the Icon

      • Currently, you've assigned a fixed height and width to the image and used a fixed padding to align it within its parent. This results in a stretched circle and is not the recommended approach.

      • To create a perfect circle and center-align the icon:

        /* Styles for the container of the image */
        height: 2rem; /* Adjust as required */
        width: 2rem; /* Equal height and width */
        border-radius: 50%; /* Makes the container a circle */
        display: flex; /* Use Flexbox for alignment */
        align-items: center; /* Vertically align the image */
        justify-content: center; /* Horizontally align the image */
        
      • With these properties, the container will form a perfect circle, and the image inside will be perfectly center-aligned without relying on fixed height, width, or padding for the image itself.


    Great work so far! Implementing these suggestions will make the UI cleaner, more accessible, and aligned with best practices. Keep it up! 🚀

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