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

Article Preview Component Solution

P
Oryan Hachamoff•440
@oryanhach
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 am proud of myself for figuring out how to add the modal using JS. I did not do the mobile modal, and the tablet and dekstop's modals displayed properly on fixed sizes, but It was not my main goal in this challenge. Overall, I am proud of myself, and while I made many mistakes during the code, I feel like I took what I needed from this challenge, and will build on those mistakes on future challenges.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Simon Cassan•280
    @SimonCassan
    Posted 5 months ago

    HTML

    • An article needs a heading to be considered valid. You could replace your paragraph "Share" with an <h2>, for example.

    • Consider adding an aria-hidden to your <div class="bottom-arrow"></div> for accessibility purposes.

    • Your article should be inside your footer so that you can position it absolutely relative to your share icon and make it responsive.

    CSS

    • cursor: pointer should be applied to .modal__img, not the entire card.

    JS

    • Adding a class that you style in your CSS makes more sense than using inline styles repeatedly.
    Marked as helpful
  • Erick Rodrigues•660
    @SortJakke
    Posted 5 months ago

    Hi, here are some comments about your project:

    General observations:

    • The share box is missing in mobile mode;
    • The share box (share__modal) is misaligned on certain screen widths;
    • The share button does not change color according to the defined design styles.

    In your HTML code:

    • I suggest placing the <img> tag inside a <figure> tag for better semantics and organization.
    • Replace the <p> tag with an <h1> in "article__description--main" to improve semantics and HTML hierarchy.
    • Placing descriptions inside a <section> or <article> tag can make the HTML more structured and SEO and accessibility friendly.

    In your CSS:

    • You used predefined declarations, which is great! However, some unnecessary declarations could be removed to reduce clutter and improve performance.

    Additional tip: To avoid misaligning the "share__modal", I recommend moving it inside the "article__footer" and applying position: relative to the footer. This will help maintain alignment and make it easier to maintain the layout.

    Final thoughts: Despite these minor adjustments, the site is very close to the original design, and the code is readable for other developers. Congratulations on the excellent work!

    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

Oops! 😬

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

Log in with GitHub