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

Article Preview Component Solution [Plain HTML and CSS]

accessibility
Faruq Abdul Hakim•580
@faruqAbdulHakim
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any suggestions on this solution are welcome. 😊

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • MoBlack00•80
    @MoBlack00
    Posted over 1 year ago

    you have done a great job bro, but I have a question how are you making it pixel-perfect like the design

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing the Article Preview Component project! You've done a great job, and it's impressive to see your progress. Here are a few tips to take your project to the next level:

    1. Use of alt Attribute in Images:

      • It's great to see alt attributes in your images, but some are missing descriptive text. The alt attribute should concisely describe the image content or function. This is crucial for accessibility and SEO. For instance, <img src="./images/drawers.jpg" alt="Drawers" aria-hidden="true"> can be <img src="./images/drawers.jpg" alt="Wooden drawers with decorative plants on top" aria-hidden="true">. Learn more about alt text at WebAIM.
    2. JavaScript Code Refactoring:

      • Your JavaScript for toggling the share options is concise and functional. Consider refactoring it to reduce repetition and enhance readability. For example, you can directly toggle the 'hide' class on shareOptions without checking if shareBtn contains the 'active' class. Explore more about JavaScript best practices at MDN Web Docs.
    3. CSS Media Queries:

      • The responsiveness of your design is crucial. Ensure that the media queries cover various screen sizes adequately. For instance, you may want to adjust the max-width in your media query for better layout on tablets. This CSS Tricks guide can be a handy reference for standard device breakpoints.

    Keep up the fantastic work and continue challenging yourself with new projects. Each step forward builds your skills and confidence as a developer. Your dedication is evident, and I'm excited to see your future creations. 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

Oops! 😬

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

Log in with GitHub