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

css toggle ids

bem
Bisshy•150
@Bisshy
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Andrey•4,600
    @dar-ju
    Posted 8 months ago

    Hi Bisshy!

    I have no comments on how you implemented the JS part, it's quite concise and elegant, you're great. But there are a few points on the html code and other.

    • why are you using the hashtag #react if you haven't used react ?
    • bem is not used quite correctly, there is a tool where you can check bem errors - tree generator
    • use the <picture> tag if you have different images for different screen resolutions, if the image is the same, then it is better to skip this tag and just use <img>
    • if time or date is used somewhere on the page, then it is semantically necessary to use the time tag, in this case like this <time datetime="2020-06-28">28 Jun 2020</time> For us, as developers, this may not be important, but search engines are guided by tags
    • links to social networks should not be just images, firstly, because they cannot be clicked, which means you need to use the <a> tag, secondly, these are clearly background images, so they need to be connected via css - background-image
    • you need to check the state of the follow button, it does not change its background and color, as in the images in the task

    Otherwise - great job, good luck with your future developments!

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