Skip to content
OverviewSolutions
21
Comments
256
P

Atif Iqbal

@atif-devPakistan3,320 points

Interested in quality web development

I’m currently learning...

professional development through frontendmentor.

Latest solutions

View more solutions

Latest comments

  • Michael Okorie•150
    @Michael-Okorie
    What are you most proud of, and what would you do differently next time?

    I’m proud of how clean and responsive the layout turned out. Implementing the share icon interaction with pure CSS and making sure the component looks great on all screen sizes felt like a real win. If I were to do it again, I’d take it a step further by building a React version with state management to practice component-based structure and interactivity.

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

    One key challenge was properly positioning and styling the share icon tooltip across different screen sizes. It required careful use of position: absolute, media queries, and some creative problem-solving to keep it responsive and user-friendly. I iterated through several versions and tested frequently to make sure the layout held up on mobile and desktop.

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

    I’d love feedback on accessibility improvements, especially regarding ARIA usage and tab navigation. Also open to suggestions on refining the transition effects for the share tooltip and optimizing the CSS structure further for reusability.

    Responsive Article Preview Card with Share Feature using Flexbox

    #accessibility#pure-css
    1
    P
    Atif Iqbal•3,320
    @atif-dev

    Congrats🎉 Michael Okorie on completing the challenge.

    You can further improve your solution by considering following points:

    • In share options(tooltip),small pointing arrow is missing. If you don't know how to make that arrow you can see this code and customize according to FEM design.
    • Active state color on share icon(your #shareIcon) is missing for mobile and desktop view.
    • For mobile view, make "SHARE" and social icons centered and bigger(see design and your solution).

    Hope the feedback is valuable for you.

    Marked as helpful
  • P
    Atif Iqbal•3,320
    @atif-dev

    Congrats🎉 Kęstutis Eirošius on completing the challenge. You did good about responsiveness.

    I would like to highlight following points:

    • You have added #react by mistake.
    • Apply border-radius on middle four images.
    • Write something useful in README file of your repo.(frontendmentor has also provided a template of README in starter files)
  • P
    Atif Iqbal•3,320
    @atif-dev

    Congrats🎉 on completing the challenge.

    You can further improve by considering following points:

    • Remove #react because your code doesn't include React structure.
    • Remove following code for proper view of images, usernames and education levels.
    .profile_info {
    display: grid
    gap: .1em;
    flex: 1;
}
    • Use LT browser, check responsiveness for tabs and improve.
    • Write something useful in README file of your code repo.
  • KrishnaPoddar1•400
    @KrishnaPoddar1
    What are you most proud of, and what would you do differently next time?

    Utilization of a grid component for the very first time.

    Would love to use it more.

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

    The styling of the mobile side went fast and I was stuck styling the desktop view.

    I faced challenges using grid as I had not structured the the card elements inside another container and tried making the whole container as grid making it congested. Later on I corrected it and the styling became easy. But then I faced the problem aligning the b2 and b3 elements. But putting them in a container made it easy.

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

    Any advice on the efficient utilization of grid would be helpful. Apart from that any other advice after looking at my code would help me a lot.

    Thank you!!

    Responsive Four Card template using HTML and CSS

    #accessibility#semantic-ui
    1
    P
    Atif Iqbal•3,320
    @atif-dev

    Congrats🎉 KrishnaPoddar1 on completing the challenge.

    • See design or picture and adjust spaces of text and images accordingly.
    • Consider using LT Browser to check responsivenesss for multiple devices and make responsive also for mid range devices like tablets.
  • Michael Okorie•150
    @Michael-Okorie
    What are you most proud of, and what would you do differently next time?

    I’m proud of how clean and responsive the design turned out across both mobile and desktop screens. I followed a mobile-first approach and used Flexbox to build the layout. If I were to do it again, I’d spend more time polishing the desktop view and maybe try using CSS Grid for more layout control.

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

    One challenge I faced was aligning the image and content side-by-side properly on larger screens. There was extra whitespace at the bottom which took time to debug. I eventually solved it by reviewing how flex containers behave with height and object-fit. Also, getting the button icon and text centered perfectly took a bit of tweaking with Flexbox alignment properties.

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

    I’d love feedback on:

    • How to improve the layout on large screens more efficiently.

    • Best practices for responsive typography.

    • Whether my use of Flexbox is optimal or if Grid would be better.

    • Any improvements to the accessibility of the button or general layout.

    Responsive product preview card using Flexbox

    #accessibility#pure-css#bem
    1
    P
    Atif Iqbal•3,320
    @atif-dev

    Hi Michael Okorie, congrats🎉 on completing the challenge.

    You nicely completed the challenge.

    I would like to highlight two points:

    • To avoid accessibility issues, follow a semantic structure. Following is a sample structure of semantic layout:
    <body>
    <main>
        ---your code here----
    </main>
  <footer>
  </footer>
</body>
    • Since we tackle responsive design in challenges so it is preferred to use em unit for padding and margin and rem unit for font-size. For further info watch this video.

    Hope you will find this Feedback Helpful.

  • Olexii Bulhakov•300
    @bulhakovolexii
    What are you most proud of, and what would you do differently next time?

    While working on this project, the most interesting part for me was customizing bullets and numbering in ordered and unordered lists. I had to use CSS counters. I had done something similar before, but a long time ago, so I had to consult the documentation to recall how it works.

    .instructions__list {
  counter-reset: item;
}

.instructions__list li::before {
  counter-increment: item;
  content: counter(item) ".";
}
    What challenges did you encounter, and how did you overcome them?

    I also tried to style the bullets using the ::marker pseudo-element, but unfortunately, it didn’t work as expected because it doesn’t support certain CSS properties, such as margin

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

    Additionally, while comparing the project with the references using the Pixel Perfect Chrome extension, I noticed that the mockups included in the project starter pack did not match the designs in Figma. Therefore, I decided to follow the Figma files instead of relying on the mockup images.

    Recipe page

    #sass/scss#bem
    1
    P
    Atif Iqbal•3,320
    @atif-dev

    Congrats🎉 on completing the challenge.

View more comments