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

Article-preview-component using sass

sass/scss
P
Mustapha•200
@Mustapha909
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?

For this challenge, I'm most proud of:

Successfully implementing a responsive layout that adapts well to different screen sizes.

Using pure HTML and Sass helped reinforce your understanding of styling with preprocessors.

Debugging layout issues and ensuring the interactive pop-up works smoothly.

Next time, I might:

Plan a more structured approach before coding to avoid layout issues later.

Experiment with CSS animations or transitions to make the pop-up appear more smoothly.

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

1️⃣ Positioning the Pop-up

Challenge: The pop-up was not positioned correctly on mobile breakpoints. Solution: Adjusted absolute positioning, used CSS media queries, and tested different flex/grid layouts to ensure responsiveness.

2️⃣ Making the Component Fully Responsive

Challenge: The layout didn't adapt well to certain screen sizes. Solution: Used flexbox/grid, fine-tuned media queries, and optimized spacing for better mobile compatibility.

3️⃣ Handling Hover and Click States

Challenge: Ensuring the pop-up appears correctly on both hover (desktop) and click (mobile). Solution: Implemented conditional Sass styles and tested behavior across devices.

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

One challenge I faced was positioning the pop-up correctly on mobile. The goal was to make it span the full width and appear at the bottom of the screen, but I couldn’t get it to work as intended. I couldn't fully resolve this issue despite experimenting with different CSS approaches. If you have any suggestions or feedback, I’d love to hear them!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Haley Underwood•190
    @underhr
    Posted 4 months ago

    it looks great! the only thing i would say is to make the container a bit wider. good job though!

    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