Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 4 years ago

HTML, SCSS, JS

SuzuMantan•370
@agusthas
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my solution to the challenge. There's some problem I encountered while finishing this challenge (mostly CSS 😢).

  • My approach on the share button tooltip was to create one HTML element and change to whom it absolutely position based on the screen size. I was thinking it will create a cleaner HTML but in CSS it create a whole new mess since i must know which parent and which child is it 🤕 . Is it better to just create two different tooltip (even though the content is nearly the same)? One for mobile and one for desktop?

Any advice on that or other things is much appreciated 🙏. Keep on coding! 🤟

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Isaay•25
    @jakubserwin
    Posted about 4 years ago

    Hi, you've done really good job. I took a look at your code and could learn some cool stuff too. Keep it up :D

    You could think about using different scss files for your variables, mixins and global styles like the 7-1 Sass pattern but in more simplified version.

    In JS if you have only 1 line of code after if/else statement you can remove brackets.

    And maybe use HTML Semantic Elements instead of divs with classes like footer and header.

  • P
    Patrick•14,265
    @palgramming
    Posted about 4 years ago

    🌟🌟🌟🌟🌟 your solution looks really good

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub