Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 16 days ago

article-preview-component-master using Javascript

Leyanis Díaz•220
@LeyaDiaz
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 how I managed to implement a fully responsive layout that adapts smoothly between mobile and desktop views using a mobile-first approach. I also feel good about how clean and organized my CSS turned out, which made it easier to adjust styles as I iterated.

If I were to do this project again, I would focus more on accessibility from the start, such as ensuring the share button is fully keyboard-accessible and adding proper ARIA labels for screen readers. Additionally, I would consider using CSS Grid for the desktop layout to experiment with different layout techniques.

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

One of the main challenges was toggling the visibility of the share bar in a way that worked well on both mobile and desktop. At first, my JavaScript logic was too simple and didn't account for different screen sizes, which caused some unexpected behavior. I overcame this by refactoring my code to use class toggling and by testing the component thoroughly at various breakpoints.

Another challenge was aligning the share icon and ensuring it looked consistent in both the info section and the share bar. I solved this by unifying the HTML structure for both icons and using flexbox for alignment, as well as adjusting the SVG sizing with CSS.

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

I would appreciate feedback on the following areas:

Accessibility: Are there improvements I can make to ensure the share functionality is accessible to all users, especially those using screen readers or navigating via keyboard?

JavaScript logic: Is there a more efficient or cleaner way to handle the toggling of the share bar between mobile and desktop?

CSS organization: Are there best practices I could follow to make my CSS even more maintainable as the project grows?

Any suggestions or code reviews in these areas would be really helpful

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Leyanis Díaz's solution.

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.