Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 28 days ago

Responsive Article Preview Component using HTML, SCSS, and JavaScript

sass/scss
Chrystiana Penalber•120
@chryspenalber
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'm most proud of how I implemented a contextual share button that behaves differently on desktop and mobile screens. It was rewarding to create a clean, responsive layout that adapts well across devices.

If I were to approach the project again, I would improve the share tooltip by adding smooth animations for opening and closing transitions.

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

Ensuring font sizes and layout elements remained fluid. I used clamp() and flexible layout units to enhance responsiveness without relying heavily on multiple breakpoints.

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

I’d appreciate guidance on handling component state and interactivity in vanilla JavaScript, particularly for adapting elements like the share button across different screen sizes in a scalable, accessible, and maintainable way, without duplicating code.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Max Kravchenko•210
    @kravamax
    Posted 26 days ago

    Good job. I hope you can find a solution for the toast component on mobile. I would recommend you not to nest CSS selectors more than two. Good luck!

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