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

CSS Flexbox, Vanilla JavaScript

Bhremada Fevreano•1,395
@boedegoat
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi, finally I done working on another fun challenge here. The result is quite great but not perfect for me. I'm not quite sure that the share popup part is already good enough or need some changes. So, any feedback would be really appreciated to help me grow. Thank you 😀

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Андрій Рогов•1,155
    @Andrii-Rohov
    Posted about 4 years ago

    Great stuff, butt he share options are clickable even if they are not visible. You should place a visibility: hidden; to a pop up options menu

  • Timothy•285
    @Timothy1982
    Posted about 4 years ago

    Hey, that's allrady looking good. Just a small side tip: If you give your social icon images a "display: block" they will align up nicer. ;) You can also include the SVG instead of linking them in the IMG tag.

  • Eric Salvi•1,350
    @ericsalvi
    Posted about 4 years ago

    Hey,

    This is a pretty solid solution. Not too much to pick apart here. Take a look at your accessibility issue reported on your solution, https://www.frontendmentor.io/solutions/css-flexbox-vanilla-javascript-D7ki7-LkQ/report Try to fix those when you can.

    The social sharing button does something weird when checking on my iPhone in landscape view. Not sure if you have a way to test on that device or not.

    The other thing I am seeing on my desktop is that the social sharing menu flashes briefly when the page loads than is hidden. Any chance you could rework it so that the social sharing menu is hidden from the start and not when the page loads?

    Other than that, keep up the momentum!

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

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