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

Article Preview Using JS

kunal90803•550
@kunal90803
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?

Trying JavaScript for the first Time.

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

I am stuck in how to handle the screen size accordingly with js and css so i made temporary adjustment to reload the page at 800px.. I know that's not the good way of solving issues but am not able to solve it.

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

An not able to handle responsiveness perfectly as if share button is clicked on small screen it does not show the similar active design on larger screen when that change the screen size whit inspect feature.. It would be really helpful if somebody tell me how did they do that in their project.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Hendrixx•430
    @BeeAlmighty
    Posted 6 months ago

    Great work kunal90803, your solution is relatively close to the design given.I love how neat your code base is and how everything belongs where they belong. Honestly, i can't see much to correct here but:

    • avoid using divs as much as possible as they interfere with web assessibilty such as screen readers and SEO.
    • I think there are shorter ways to write the javascript you wrote but kudos to you because you said it's your first time and the code works as well. Great work!
    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