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

Article Preview Component

bem
P
Josephine Fitalvo•280
@fitalvojosephine
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 proud of my ability to combine HTML, CSS Grid, Flexbox, and transformations (translate along the X and Y axes and scale) to make the share button hide the element, along with using DOM JavaScript. I accomplished this by researching and reading other developers' code to complete an article preview component. I structured it responsively and added basic JavaScript functionalities using addEventListener.

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

I encountered some difficulties with the button, specifically with how to make it hide, transform, and translate on hover and when clicked by the user. I researched this issue and resolved it by studying other developers' code. Additionally, I had some challenges with the grid-template-columns property for the container size. To fix this, I decided to use grid-template-columns: 285px minmax(300px, 445px);. This means the first column will always be 285 pixels wide, while the second column will have a flexible width that adjusts between 300 pixels and 445 pixels, depending on the available space in the container. This solution works perfectly.

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

So far, none. Kindly give me some feedback to improve my coding skills. Thank you! #HappyCodingEveryone

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bisshy•150
    @Bisshy
    Posted 12 months ago

    Nice job your naming sense with the BEM method and your styling are good I learnt some new skills from you, I checked your page and I found out that your card__share-option is by default active when it's visited you can turn it off by adding the hidden class to the div of your html file which carries the icon images and adding the hidden class to you css and style it with the display none. i don't know if your JS will still work after this adjustments but if it doesn't try

    "shareButton.addEventListener("click", function () { shareOption.classList.toggle("hidden");" }); that is you set thet the shareButton to display the hidden card__share-options and you can fine-tune your css html also by removing the active class. I learnt a lot from your naming convention and I hope this I wrote up on here helps 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

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