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

Article Preview |HTML| |CSS| |JS|

Abhi•490
@abhi-zero
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?

This is my first project with JavaScript. Working with JavaScript is difficult for me, but it’s interesting.

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

A little bit of challenge occurs during development, but I fix most of those issues myself, and I take a little help from GPT.

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

Mmm, this is my first project, so I don’t know much about how to handle JavaScript. My logic is simple: when user click the button, it adds a class to the share section, which has two wrappers—one for mobile and one for desktop. I created a class called 'hide' with the CSS rule display: hide; (I know, what was I thinking?). This 'hide' class is the initial state, and when the user clicks the button, it removes the 'hide' class and adds the appropriate wrapper class according to the window size.

I’m sure I’ll improve my skills faster than a squirrel on an espresso! Any feedback or suggestions are welcome!"

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ataize Feitosa•260
    @Ataize
    Posted 8 months ago

    Hello everything is fine?

    I'm just a beginner, but I think you could optimize your javascript by adding/removing classes in a more concise way, using toggle.

    The toggle method toggles the presence of the hidden class in the element every time the button is clicked.

    I hope I helped and keep it up.

    Marked as helpful
  • Fikerte Tesfaye•280
    @Fikerte-T
    Posted 8 months ago

    Congratulations!! Your solution looks great.

    Keep up the good work!! happy coding

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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