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

Article Preview Component with Javascript and Font Awesome

Osiel Hernández•190
@xXOsielXx
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 very happy to have used CSS nesting. I was using it with SASS in a past project because I didn't know that it exist in CSS, but recently I found out and now I'm working faster.

I was using Font Awesome too. I like this icon library. Is too easy to set icons with it.

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

It was difficult to work with the image. I spent a lot of time on it.

The social networks container was difficult to work with, especially their styles in desktop. But hey, I learn how to make arrows with css...

.share-container::before {
        content: "";
        position: absolute;
        left: 50%;
        bottom: -14px;
        margin-left: -16px;
        border-left: 16px solid transparent;
        border-right: 16px solid transparent;
        border-top: 16px solid var(--very-dark-grayish-blue);
}

and a nice transition...

.share-container {
        transition: top .4s, opacity .4s;
}
What specific areas of your project would you like help with?

I need help with the image. Can you tell me how I can position the image so that it looks exactly like the design? I'll really appreciate it.

Any other thing would be nice :D

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • haquanq•1,655
    @haquanq
    Posted 12 months ago

    Hellooooo @xXOsielXx 👋👋👋

    About your feedback request, have you tried object-position ?

    Here is some other things that can be improved:

    • Each page should have one main landmark which means wrap you most important content of the page inside it (there are other landmarks).
    • Using more semantic HTML markups and keep your HTML simple (avoid unnecessary wrapping elements - using too many div). For example, repetitive piece of content can be grouped by ul li to indicate the relation between each of them (same role depend to the context, maybe a list of links, a list of todo items).
    • figure is being misused here, figure is often used along with figcaption and wraps around contents to give it extra details/explanations (SEO and accessibility improvement ) - could think of it simply as a label/caption (not only for images, can be a list, a long paragraph,... ). Here you are using figure for an image with zero context and it is redundant, leave only the img alone is fine.

    Hope this help 🙀🙀

    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
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