Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

article-preview-component-master solution

Philip Droubi•585
@Philip-Droubi
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey everyone 🙋‍♂️, this is my solution for article-preview-component challenge.

Please take a look and give me your feedback. Thanks :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    visualdennis•8,375
    @visualdenniss
    Posted over 2 years ago

    Your solution looks great. I don't have any suggestion to add as your version already pretty good. I especially like the spinning arrow icon on click!

    If you look for further inspo, you could add a hover effect to the image, e.g. on hover image could scale up a bit like 1.02 or so. Also you could change the arrow icon background color with a smooth transition on hover as well. Additionally, the icons section could appear with a slight animation from opacity 0 to opacity 1 and y 5 to y 0, basically a small fade-up animation. These are just some ideas to add on top if you prefer :)

    Hope you find this feedback helpful!

    Marked as helpful
  • Aruj Joshi•290
    @gtalin
    Posted over 2 years ago

    Really like your solution for the component specially the animation for the button. You have also used aria-label for the button which is really important for accessibility for someone who uses a screen reader.

    I just have one small feedback. You have removed the default outline from the button because of which there is no visual cue for someone who uses a keyboard to navigate the website. It is not a good idea to remove outline from buttons and a tags because it makes it difficult for people who only use a keyboard for navigation. And if you do remove the default outline on focus, it is best to add an alternate.

    Hope the feedback was 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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub