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

article-preview-component

calvinvin•1,170
@calvinvin
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?

It took me a while to re-design the HTML and CSS when starting mobile design after finishing desktop design (basically where the wrapper/container divs should be). I should inspect the design images more carefully and think more thoroughly before I start writing codes.

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

What I learned:

  1. how to make triangle shape by setting border properties on a div.
  2. more familiar with "position: absolute", "transform: ...", "object-position" CSS properties.
  3. the use of <svg>. I should use <svg> tag instead of import the svg by <img> or <object>, so that I can change the "fill" property (the color of curved arrow on share-button) by CSS.
  4. Any click event on <object> element would be captured by whatever is inside the <object> element, and doesn't bubble it back out. So in order to make icon-facebook (which is imported by <object> element) part of <a> element and clickable, I just have to add "pointer-events: none" to the <object> element.
  5. I should use "visibility: hidden" instead of "display: none" on div.share-links-wrapper when share-button not active. If I pop up the div.share-links-wrapper by changing "display: none" to "display: flex", the layout was re-calculated and cause a transient whole layout shift during transition.
  6. to make an element visible when overlapped with "position: absolute" element, I just need to set "position: relative" and increase the Z-index on the element.
What specific areas of your project would you like help with?

What's the exact layout method that align the drawers image and the article content? I use grid with "grid-template-columns: auto auto", but the widths of the two components were not the same as example.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • tiedej2000•340
    @tiedej2000
    Posted 8 months ago

    excellent execution :)

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

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