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

Article Preview Component (desktop-first approach)

LonlySoft•170
@Lonlysoft
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?

pretty proud on How I made the arrow in the desktop mode. ::after and ::before may seem pretty confusing to use when you don't have any idea of what you're doing, but after some quick explanation I could make the arrow without inline SVGs and the positioning process that they come with. I also brought up sone animations that pretty much work as intended.

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

This was the hardest challenge so far. A simple design, but it hides a very specific thing: the sharing component. at first I thought on doing a position: absolute manipulation using left and top to perfectly position where the icon was using em measuring type, however I noticed a thing: that wouldn't be responsive. since the other screens would result in the component going to unexpected places. so I gone consistent and put the share component content inside the share icon so It could get their relative positioning and always appear on top of the icon. But that cost an entire week of me trying to position it in the mobile mode. the mobile mode isn't that sophisticated so I did the only thing that passed through my mind at that time: copy and paste the element and add the share icon. But that's also not the hardest thing yet. There's also the use of event.stopPropagation method to actually exit the share mode. There's actually nothing saying that you should do that with the component but since there's nothing indicating how you close the share component, I just did the most obvious system.

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

Well, one of the stuff that I'm sure with a headache for is a problem happening with the mobile version: When you touch on the share icon the share component opens normally, but when you touch on the share component, it disappears. any link I placed there works, but I just find pretty odd this type of thing happening. I made use of the stop propagation to stop this from happening, that made this doesn't happen on desktop mode, but in the end it still persists in mobile.

I still don't have any clue on how to resolve this.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted 6 months ago

    The height needs to be adjusted too

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