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

Article preview component

Zi•150
@code269
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 feel like I was able to get the style very close to the design. I paid close attention to small spacing and sizing details.

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

Learning how to properly position the button popup and getting to apply the onclick event were the most challenging parts of the project. I was able to learn a lot about how positioning works and do a little bit of limit testing on DOM manipulation.

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

For this challenge, my biggest issue was not being able to only have one on-click button. In my solution, I ended up doing a band-aid solution with two different buttons (original button and the popup button) which I never really resolved, partially because I started this assignment a few months ago and wanted to keep what I had initially to get properly critiqued. Any suggestions or pointers on a different approach would be a big help!

As usual, any suggestions on changing/improving naming philosophies such as how to properly apply BEM to my HTML and structuring would also be greatly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • asthaaaaa07•40
    @asthaaaaa07
    Posted about 2 months ago

    Hi there! 👋

    First off, I just want to say that this is a beautifully structured and clean solution. The layout looks great across screen sizes, and your use of BEM conventions, CSS variables, and media queries is really solid — great job! 👏

    That said, I noticed a small issue worth fixing: In your CSS, the font-family is currently written as: font-family: 'Maonrope', sans-serif; However, the correct font name (as loaded from Google Fonts) is: font-family: 'Manrope', sans-serif; Just a tiny typo, but correcting it will ensure your font loads and displays as intended. 😊

    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