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

Article preview component

accessibility
Yamien Ariel•210
@ariel172
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'm proud to have finished this challenge on time, unlike the previous one, I'm proud to have written JavaSvript. Next time I'll do better in the responsive because at some level the social network menu is not correctly displayed.

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

I've encountered challenges in responsive when clicking on the arrow to share the menu that appears is not correctly displayed on some screen sizes. I couldn't fix it, I made it responsive on a certain size.

What specific areas of your project would you like help with?

Responsive! It's as if I had to make it for every pixel to display the social network menu properly.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marcos Travaglini•6,230
    @Blackpachamame
    Posted 5 months ago

    If you want to keep your footer down using position: absolute then you don't need to use margin-top. Instead, just use bottom:0. This will make your footer stick to the bottom, if you want to leave some space then instead of "0" you can put a value, for example bottom:10px, this way your footer will be 10px off the bottom.

    Marked as helpful
  • Yamien Ariel•210
    @ariel172
    Posted 5 months ago

    Thank you very much, I'll take this modification and apply it to my code to see exactly how it turns out.

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