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

Article Preview Component Master

JJ-codes-9•110
@JJ-codes-9
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 the overall layout and styling came together, particularly the clean and visually appealing design. It feels rewarding to see the responsiveness on larger screens working as intended. Next time, I would focus more on planning the interactive elements in advance and testing them on various devices early in the process. I also want to explore using CSS animations or transitions to enhance the user experience further.

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

The biggest challenge was figuring out how to create the interaction that enables the popup to toggle when clicked. It required a good understanding of JavaScript and how to manipulate the DOM dynamically. Another challenge was making the layout responsive, especially ensuring the elements align properly in mobile view. I tackled these by breaking the problems into smaller steps—debugging and testing the popup logic separately before integrating it—and refining the CSS media queries for better responsiveness.

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

Currently, the popup doesn’t work in mobile view, and I couldn’t figure out why. I suspect it might be an issue with how the JavaScript interacts with the layout in the smaller viewport. I’ll continue to troubleshoot this, but I’m open to suggestions from the community on how to resolve it or improve the way I’ve structured the interactive elements. Additionally, any tips on optimizing the layout further for mobile users would be greatly appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • h3cat3•330
    @h3cat3
    Posted 8 months ago

    You have done a great work. I've done a quick investigation using my browser's developer tool, it looks like your popup does work in mobile view, but because of the position: relative; top: 12rem; is showing somewhere outside of the scrin area.

    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

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