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

Article Preview Component using JS and SASS/SCSS

sass/scss
P
Van Tu•270
@imvan2
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'm most proud of getting the JS down, but I would work on my refactoring skills in the future.

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

I had trouble matching the styles of the 'Share' toast for tablets and desktops, so I used an image instead. Wasn't sure if this was the way, but my toast isn't 100% accurate to the designs even so.

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

I feel like my SASS files are a little long? If there is some way to keep it short and concise while still keeping the styles, I would love to know!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Davy•320
    @DavyZane
    Posted about 1 month ago

    Hello,

    The path you took for this project seems long and winding. You structured your files as if it were a huge project (which can be a very good practice), despite the "simplicity" of the project. In the end, you did not succeed to perfectly reproduce the model.

    As a beginner myself, I attempted this project three times, several weeks apart. During my first two attempts, I got into complicated code and ended up getting lost and giving up. It was only on the third attempt that I succeeded, by thinking ahead about how I was going to manage everything and, above all, without rushing.

    If I have one piece of advice to give you, it's to keep things as simple as possible, keeping the goal in mind, of course. I invite you to take a look at my project, my code, and the commit history, I think you'll find some interesting elements.

    I wouldn't say your project isn't perfect, but rather that it's not finished. Don't give up! In any case, you've done a great job!

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