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

Article Preview with HTML, CSS and JS

errbrokko•80
@errbrokko
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 proud that I got it running because this one was tougher than the ones before. It's still not perfect though.

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

Combining Javascript and CSS for responsive layouts was tough. I did not solve my problem fully. See below.

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

I would like to know how to effectively combine Javascript and CSS in this case. Although my solution seems to work at first, it does run into problems when I toggle a state and then switch from mobile to desktop viewport or vice versa.

Also, how do I get the "bubble look" for a popup?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Felix•300
    @felix-stuff
    Posted about 1 year ago

    Hi @errbrokko, I just looked at your solution. It's quite far, but some of the CSS spacing needs a closer look and for the mobile version there are some issues with the popup and the overall design of the card.

    For your questions on how to combine JS and CSS in this case I would recommend reducing the JS to a bare minimum. In my solution I only use one event listener to toggle the share popups visibility. The rest is all done by CSS.

    For the bubble look you are only missing on the little arrow at the bottom of your popup. Maybe check out https://cssarrowplease.com to see how you can use the border property in CSS to create this type of arrow.

    Another thing worth checking out might be the details of position absolute. In my solution I repositioned the popup to be visible in the center of the screen on mobile and moved the little arrow to the right so that its above the share button.

    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