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

Article Preview Component - Solution

sass/scss
P
thibault.deverge•310
@thibault-deverge
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • vladyslav-shulhach•190
    @vladyslav-shulhach
    Posted 5 months ago

    Great job on your project! The design is excellent – every element fits perfectly into the proposed layout, and your attention to detail is impressive. I was particularly impressed by your well-organised SCSS. It has a clear structure that makes maintenance easier, and it means that we don't have to scroll through endless code to look for or fix things. Your approach is both elegant and efficient, and I'm inspired to adopt similar practices in my own projects, especially the bigger ones.

    Well done on utilising the BEM methodology. It makes the code so much easier to work with, and it's great to see such a well-structured approach in action.

    I have a few suggestions on how you could further enhance your code and workflow in future projects:

    • Accessibility:
      When you're developing a website, it's really important to not overlook accessibility. If you provide meaningful descriptions, it'll improve the experience for users who rely on assistive technologies and it'll also be better for SEO. Instead of leaving the alt attributes empty or using aria-hidden="true", it's better to include descriptive text. For example, rather than hiding the Facebook icon from screen readers, you could add alt="Facebook icon" so that assistive technologies can recognise it.

    • User Interaction:
      The social share panel opens when clicking the button, which is great. But it would be even better if it also closed when clicking outside of it or pressing the Esc key. If you could make it so that JavaScript could do this, it would make it feel more user-friendly.

    Overall, you have done an amazing job. Keep up the excellent work, and happy coding!

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