Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Article preview component

alvarozama•360
@alvarozama
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?

Not much to feel proud of this time around since I was barely able to complete the challenge and my solution is extremely far from perfect as evidenced by the various bugs I was unable to fix. As far as what I would do differently next time, I guess I'd try to organize my markup elements in a much more concise way that also allows to retrieve them from the DOM more coherently.

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

Lots of challenges, but the biggest one was basically making the share button display different things according to the viewport size. I was able to overcome this by using the window.matchMedia() method and assinging the value of a desired breakpoint to a variable which was later used on a function that would work differently based on wether or not the screen size matched the one assigned to the variable.

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

While the solution to the problem previously outlined kind of worked, it only did so when loading the page on a certain screen size and sticking to it. Loading the page on a mobile display would make the share button work as long as one remained on that display. However, when trying to go from mobile to desktop display or viceversa, the behaviors of the button would overlap and the speech bubble meant for desktop display would show on mobile, or the SNS bar meant for mobile would show on desktop. I had no idea how to solve this problem and would appreciate some insights on what I coul do differently.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Rohan Tayal•310
    @rohantayal
    Posted about 1 year ago

    You could apply overflow: hidden to your relative-anchor class for mobile and tablet layouts.

    That solves the mobile and tablet layout but then we face the similar issue in desktop layout.

    You can check out my solution and see if it helps. I couldn't think of any other alternatives asie from modifying the entire HTML structure.

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