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

Article preview component

Abdullah Zafar•180
@ei-abdullah
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 proud of integrating HTML, CSS, and JavaScript to create a responsive web component. Next time, I'll improve CSS organization for better scalability and deepen JavaScript skills for advanced functionality. This project fuels my passion for web development, driving me to excel in user-centric digital solutions.

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

When encountering web interactivity challenges with JavaScript for the first time in a while, I faced difficulties primarily with styling issues. Overcoming this hurdle involved a combination of debugging, consulting documentation, and experimenting with CSS adjustments to achieve the desired visual and interactive outcomes, although, it is not as perfect is it was given in the design file.

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

I would appreciate help particularly in two areas: responsive design to ensure my project looks great across various devices, and enhancing JavaScript interactivity to create smoother user experiences. These aspects are crucial for improving the functionality and accessibility of my project, and any guidance would be invaluable in refining these skills.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matt Cope•350
    @MatthewPCope
    Posted about 1 year ago

    Great job! There are a couple spacing and font size issues. You could lower the main-container gap, right now it's 20 px so try to lower that and in the media query lower the font sizes of description1 and description2. The button functionality is a little off too but not exactly sure how I would fix that here. Hope any of that helps!

    Marked as helpful

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