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

Responsive Article Component with Scss and JS

sass/scss, bem
Sergio Eduardo Castro Ceballos•350
@SergioCasCeb
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 like implementing small interaction like closing the social media links elements if the user click outside of the links container. Not necessarily something to be proud of, but I believe that small things like this can make the difference.

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

My main time consuming task of this project was deciding how to structure the whole layout in HTML, so that later on when implementing the interactive social media links elements I would be easier. At the end I decided to make the links element a child of the user section, so that it would interact in relation to that specific part of the component.

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

Nothing in specific, but feedback is always welcome. If you also utilized a simpler or more fun approach, I would love to hear about it. Seeing how other tackle the same challenge is always fun.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Francisco•210
    @antoniomontoia
    Posted 8 months ago

    Feedback Summary:

    Semantic HTML: Good use of semantic elements like <main>, <article>, and <footer>. Consider adding <section> for related content.

    Accessibility: Great use of aria-labels and keyboard accessibility. Ensure all interactive elements are focusable and have clear focus styles. Add more descriptive alt text for images.

    Responsive Layout: The layout is generally responsive, but the mobile/vertical version of the card is not, for that the image is overflowing. Removing max-height from img and setting a max-width for the card would do the trick.

    Code Structure: Well-structured and readable code.

    Overall, you nailed the hardest part with the JavaScript implementation—great job! In my case, using an icon would have saved me a lot of trouble, and I'm going to review my solution right away!

    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