Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Article Preview Component

Jarrod Ver Hey•150
@jvisme1991
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 am most proud of completing my first challenge that included using javascript.

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

Using js without knowing any of the fundamentals was a nightmare. I will definitely work more with js to gain a better familiarity with it for future use.

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

I would most definitely like more help with js.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • CJ Cameron•350
    @CJCameron13
    Posted about 1 year ago

    Nice work! Another approach you could use is the classList.toggle feature to achieve the same functionality that you currently have. I like to add a class called 'hidden' to the element and in my CSS document, given .hidden the attribute of display:none.

    .hidden {
    display: none; 
    }
    

    Using your shareButton and shareLinks identifier, the JS code would look something like this...

    shareButton.addEventListener('click', () => {
    shareLinks.classList.toggle('hidden')
    }
    
    Now the 'hidden" class will toggle on and off with each click by the user.
    
    Just my preferred method. Well done with the project!
    
    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 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