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

html, css & js solution

hannerr•100
@hannerr
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 have a quite usable template for card layouts by now, which I can reuse.

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

I realized that positioning items absolute brings quite some issues with padding, you have to keep in mind, that padding influences the position.

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

Positioning. I would like to see an expert solution

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    yoyov51234•240
    @yoyov51234
    Posted about 1 year ago

    Hi There~ Good implementation! I get some inspiration from your code, like to separate some div out ( the author info, to the bottom, only by itself), so that it the mobile banner will be easier displayed.

    Some suggestions: 1- when using dev tool of Chrome(F12), i always see the mobile version, not the desktop version, even my responsive screen was set as '1208px' wide, that's caused by this code: @media screen and (min-width: 1440px) {}, seems it's to large to display the desktop view,

    Laptops and Desktops 1280x800: Small laptops (e.g., some netbooks). 1366x768: Common laptop resolution. 1440x900: Some laptops and monitors. 1920x1080: Full HD resolution, very common for desktops and larger laptops. 2560x1440: Higher resolution monitors (QHD). 3840x2160: 4K resolution monitors and TVs.

    2- In the mobile view, this title: 'shift the overall look and feel ..' has no paddings, so it starts from the left and shows a different layout than others.

    3- On mobile view, in the share banner, there's a share icon, it's not aligned with other icons. - This can be solved by changing the layout, and using flex.

    4- On desktop view, the share banner's position is not quite right.

    Regarding on the position part, I'd like to have a voice chat so that we can share the screen and discuss on it. : ) please let me know if you are interested.

    (PS: English is not my mother tongue, could please kindly point out if any comments mislead you, thank 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