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

Article Preview Component

sass/scss
P
gajbos99•170
@gajbos99
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?

/

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

/

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

Well i ran into a couple problems. first of all. i created mobile first and created the design for both of the share parts. i just do not know how to change that when full screen as that is looking different. the mobile social media icon div is looking different from the one on the desktop. What is the best way to do that? as now i put display none on the light share bar and display flex on the other one and that toggles. but on the desktop version the light one doesnt need to be removed.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mateus Lima•490
    @mts-ml
    Posted 10 months ago

    Hey @gajbos99!

    I liked that you used React and useState. I've used JS to manipulate the class, but using the hook seems better.

    I tried to preview the solution site but got a 404 error. Looking at the code, I noticed that you jumped from a <h1> to a <h4>. I've read that you should always follow header hierarchy.

    The solution differs a little from the design; the background color is off, and the name/date is centered when it should be aligned to the left.

    About your question, I’d need to see the page and play around with it a bit to try and provide some input.

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