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

Article preview component solution

sass/scss
larryQuao•130
@larryQuao
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?

Able to complete this challenge

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

I had challenges with the javascript DOM, but I was able achieve what I wanted to do and it worked. I have to practice more to be conversant with it.

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

Understanding more about Javascript DOM

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Williams Akanni•350
    @shadowbanks
    Posted 5 months ago

    Hii,

    Great job on completing the challenge Larry 🥳

    I have a few suggestions for you :))

    1. Currently, you're using an h3 tag for the date<h3 class="date">28 Jun 2020</h3>. A better option could be the time tag <time datetime="2020-06-28">28 Jun 2020</time>. for improved semantic HTML and SEO.

    2. Right now, you have the active part as the default view, removing is-open from the class will do the trick.

     <section class="share-content is-open">
    
    1. In your javaScript I noticed that body.classList.toggle('is-open'); doesn't actually have any visible effect, as you're not styling it in the CSS

    Additionally, I have a suggestion for your code, you can create a function to handle the classes toggle, which would make the code cleaner and more reusable. Here's how you could do it:

    const toggleIsOpen = () => {
      shareContent.classList.toggle('is-open');
      authorDetails.classList.toggle('hidden');
    }
    
    shareButton.addEventListener('click', () => {
      toggleIsOpen();
    });
    
    // Add a separate event listener for the dark share button
    shareButtonDark.addEventListener('click', () => {
      toggleIsOpen();
    });
    

    This way you won't need the extra .remove calls. It simplifies things a bit and keeps your code DRY (Don’t Repeat Yourself).

    I hope this is helpful, happy coding!😊

    Marked as helpful
  • larryQuao•130
    @larryQuao
    Posted 5 months ago

    Noted, I will get back on it an do the suggested correction you have stated. Thank you

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