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

Article preview component

CoolNight99•440
@CoolNight99
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 think I got the design and functionality pretty close.

What challenges did you encounter, and how did you overcome them?

I struggled with creating the tooltip. I used position: absolute but I'm not sure if that was the correct approach.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Car•270
    @Lukas3162000
    Posted 8 months ago

    Great job on this submission! The design is really well-executed, and it’s clear that you’ve put a lot of effort into getting it as close to the original as possible. The overall layout looks clean and professional, and the functionality appears to work seamlessly, which is a big plus.

    Your tooltip implementation is clever, and it integrates nicely into the design. If you’re unsure about using position: absolute, don’t worry—it’s a valid approach, but experimenting with position: relative in combination with flexible parent containers might make the positioning more adaptable, especially for responsive layouts. Speaking of responsiveness, separating the logic for desktop and mobile behavior more distinctly could make your code easier to manage and fine-tune for different screen sizes.

    Overall, this is an excellent submission, and you should be proud of how close you’ve come to matching the design and functionality. Keep up the great work, and best of luck with future challenges! 😊

    Marked as helpful
  • Mayssa Ghanmi•170
    @MAY55A
    Posted 8 months ago

    Nice effort, here are some changes to consider:

    • add semantic HTML (at least a main tag) and alternate texts to images for better accessibility.
    • make the container and the font smaller to match the design.
    • instead of defining the width of the article container by specifying a margin, just try specifying a width so it stays constant even when the screen size is changing.
    • try adjusting the width of the image when the screen is smaller by giving it a width relative to the total card width ( you can use % for example).
    • try positioning the share div exactly on top of the author div for the mobile layout and making the share div invisible.

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