Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
16
Comments
20
PIYUSH KUSHWAH
@piyushkumarx

All comments

  • DamaniSahu•150
    @DamaniSahu
    Submitted 19 days ago

    Result Summary Component

    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted 19 days ago

    great

  • José Alfonzo•370
    @JoseAlfonzo92
    Submitted 21 days ago
    What specific areas of your project would you like help with?

    It's a basic challenge, so no need for help at the moment — but if you spot anything off or see areas I could improve, I'd love your feedback. Always open to refining things.

    Stats preview card component using HTML and CSS

    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted 19 days ago

    Areas to Improve: Padding on Small Screens:

    On very narrow screens (less than 350px), the text feels a bit too close to the edges. 👉 Add more padding: 1rem or margin-inline: auto to improve breathing room.

    Stats Layout on Mobile:

    Currently, the stats are in one row on mobile, which can feel tight. 👉 Consider stacking the stats vertically (column direction) for better readability on narrow screens.

    Font Size Scaling:

    The paragraph font size could scale slightly smaller on mobile to prevent long lines from wrapping awkwardly.

    Container Width Limit:

    On very large screens (e.g., 1440px+), the card looks too narrow in the center. 👉 You could make the max-width a bit wider or add a slight zoom effect to better use screen space.

    Marked as helpful
  • Priya•90
    @Priya-lak
    Submitted 19 days ago

    product-preview-card-component-main

    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted 19 days ago

    Hey ,

    I came across your frontend project (link) on GitHub and wanted to say it's really well done — especially the layout and responsiveness!

  • AzumiA•20
    @azumia-azu
    Submitted 25 days ago

    Blog preview card solution

    #pure-css
    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted 25 days ago

    It's impressive! Just make sure to make it responsive across devices.

  • P
    Raul Rodriguez•200
    @santi-rdz
    Submitted about 1 month ago

    Use of CSS Grid - Flex, min, clamp

    #pure-css
    2
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 1 month ago

    ✅ What’s Good: Clean & modern layout — Follows the bento grid trend nicely.

    Responsive design — Looks great on all screen sizes.

    Well-organized — Good use of spacing and alignment.

    🔧 Suggestions: Highlight key sections — Use size or color to show importance.

    Add hover effects — Improves interactivity and feel.

    Check text contrast — For better readability and accessibility.

    Optimize performance — Lazy-load images and minify assets.

  • Virshree Desai•250
    @Virshree
    Submitted about 1 month ago
    What are you most proud of, and what would you do differently next time?

    I am proud of completing this challenge.

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

    Nothing..

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

    Any suggestion or improvements are welcome..

    Bento grid -Responsive css grid

    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 1 month ago

    Hey brother, you did a great job! I’d love to talk more about this project. Here’s my Instagram — feel free to DM me: @piyush.kumarx

  • Mohamed Ahmed Al-Shrafi•140
    @mohammed-al-shrafi
    Submitted about 1 month ago

    Testimonials Grid Section

    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 1 month ago

    Great job on building the Testimonials Grid Section! 🙌

    ✅ What you did well:

    The layout looks clean and well-structured.

    The use of grid is excellent — it creates a balanced and organized look.

    Color contrast is good, making the text easy to read.

    The design closely matches the original challenge — well done on the attention to detail.

    🔧 Suggestions for improvement:

    Consider adding hover effects or a little animation to make it more interactive.

    It would be great to make the layout responsive for smaller screens (like mobile phones).

    Add alt text for images (if any in the full version) to improve accessibility.

    Overall, it's a solid project that shows you have a good grasp of HTML and CSS layout techniques. Keep experimenting and adding new features — you're on the right path!

  • Komal Jatoi•210
    @komaljatoi
    Submitted about 1 month ago

    Four Card Feature

    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 1 month ago

    Your code is clean and easy to understand. The layout looks good, and the colors match well. You’ve used the basic structure correctly, which shows you understand how HTML and CSS work together.

    To improve even more, you can:

    Use better spacing and font sizes to improve readability.

    Overall, it's a solid project. Keep practicing and learning — you're doing great!

    Marked as helpful
  • edelance21•180
    @edelance21
    Submitted about 2 months ago

    Product preview card component.

    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 2 months ago

    👍 Good: Clean, minimal design.

    Nice typography and layout.

    Clear pricing with discount shown well.

    🔧 Improve: Mobile view needs better spacing and font scaling.

    Add hover/focus effects on the button for better UX.

    Slightly enhance responsiveness with media queries.

    Great work overall!

  • TiWiX•40
    @TiiWiX
    Submitted about 2 months ago
    What are you most proud of, and what would you do differently next time?

    I really managed the page layout, without abusing of Flexbox or CSS Grid. Just using margin, padding, etc. It's very responsive moreover

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

    Better ways to manage the layout, to make it responsive, etc.

    A solution to the recipe page challenge

    2
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 2 months ago

    it's good and looking exactly same but you have to work on responsiveness

  • WalaNour•10
    @WalaNour
    Submitted about 2 months ago
    What are you most proud of, and what would you do differently next time?

    deploing my website

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

    the first time using github page and netlify and it was sooo challenging then it ends up by searching how to

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

    nothing for now

    responsive landing pages

    2
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 2 months ago

    ✅ Semantic HTML You use proper semantic elements like <main> and <section>, which is great.

    ♿ Accessibility Good start with alt text and labels. To improve:

    Add focus indicators

    Ensure keyboard navigation

    Check color contrast

    📱 Responsive Design Layout works well on different screen sizes. Consider using more relative units and refining media queries.

    🧱 Code Quality Clean and readable. You could improve reusability with modular CSS or components if using a framework.

    🎨 Design Match The implementation aligns well with design. Keep styles consistent using design tokens or a style guide.

    Suggestions: Add form validation, improve performance, and consider fallback behavior if JavaScript is disabled.

    Great job overall!

  • Asya0601•280
    @Asya0601
    Submitted about 2 months ago

    Perfume card in the basket

    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 2 months ago

    Semantic HTML Good use of semantic tags like <main>, <section>, <h1>, <p>, and <button>.

    Ensure all images have descriptive alt attributes for better accessibility.

    Consider adding aria-label to the "Add to Cart" button for screen readers.

    Accessibility Mostly accessible due to semantic structure.

    Missing meaningful alt text on some images; add descriptive alts or empty alt="" for decorative images.

    Confirm all interactive elements are keyboard navigable and focusable.

    Button icons without text need proper labels or aria-hidden where appropriate.

    Responsiveness The layout adapts well to different screen sizes.

    Could improve by using <picture> element or srcset for responsive images.

    Media queries handle layout shifts nicely; spacing and text size scale well on mobile.

    Code Quality Code is clean, readable, and well-organized.

    CSS can be improved by adopting a methodology like BEM for class naming.

    Consider modular CSS for reusability and maintainability.

    Keep consistent indentation and comment sections if the code grows.

    Design Fidelity The design matches the original mockup closely.

    Colors, typography, and spacing are well replicated.

    Minor improvements: double-check font imports and exact spacing for pixel-perfect matching.

    Marked as helpful
  • morning-rgb•150
    @morning-rgb
    Submitted about 2 months ago

    Product Preview Card using Webpack, Pug, CSS

    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 2 months ago

    Great job on this project! The design is clean, visually appealing, and very user-friendly. It's fully responsive across different devices, which shows the attention to detail and effort you put into making sure everything works perfectly. All the elements are well-aligned, and the overall layout is consistent and professional. Excellent work – everything looks spot on!

  • Twilight Silver•120
    @twilight-silver
    Submitted about 2 months ago
    What are you most proud of, and what would you do differently next time?

    Soooo this time i used bootstrap to work out the design and it came out really really nice

    Responsive Recipe Page

    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 2 months ago

    You didn’t create the design exactly as shown in the image, but I appreciate the effort you put into it. You tried well—keep practicing and paying attention to the details. You're improving, and that’s what matters most. Keep it up!

  • PhuLookingGood•30
    @PhuLookingGood
    Submitted 2 months ago

    Recipe page using HTML CSS (grid)

    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 2 months ago

    your live site link is not working !

  • Talal Amir•130
    @Talal-Amir
    Submitted about 2 months ago

    I created a responsive social links card using HTML and CSS.

    2
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 2 months ago

    Thanks for sharing your work! It’s clear that you put in effort and applied what you’ve learned so far, which is always something to be proud of. Taking the initiative to build something from scratch is a valuable step in growing your skills.

    That said, I noticed the project isn’t responsive and lacks hover effects. These are small details, but they can make a big difference in the user experience. Don’t worry—these are common things to overlook, especially early on. The important part is that you recognize them and use this as a learning opportunity for next time.

    Keep it up! You're building a solid foundation—just remember to test your designs on different screen sizes and add interactive elements like hover states to enhance usability and polish. Great start overall!

    Marked as helpful
  • Ashik_Ridwan•30
    @ashik-2534
    Submitted about 2 months ago
    What are you most proud of, and what would you do differently next time?

    I am proud of that I tried to do it myself based on the knowledge I have. And I turned out pretty well.

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

    But it wasn't felling like eye catching so I used AI to refactor the code tweak some styles and added a hover effect.

    Blog preview card

    2
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 2 months ago

    Thanks for sharing your experience! It's great to hear that you took the initiative to build the dashboard using your own knowledge—that's definitely something to be proud of. It shows a strong willingness to learn and apply skills independently.

    I also really like how you identified what wasn’t working visually and took steps to improve it using AI. That kind of problem-solving mindset is really valuable. Using AI to enhance design and functionality is a smart move, especially when you're working solo.

    For next time, you might consider experimenting with design inspiration or layout planning early on to make the visuals pop right from the start—but overall, great job! Keep building and refining—you're definitely on the right track.

  • Shubham Giri•30
    @XshubhamG
    Submitted about 2 months ago

    Social links Dashboard using HTML and TailwindCSS

    #tailwind-css#vite#node
    1
    PIYUSH KUSHWAH•310
    @piyushkumarx
    Posted about 2 months ago

    I recently came across this Social Links Dashboard built using HTML and TailwindCSS, and I must say—I'm thoroughly impressed! The design is sleek and minimalistic, yet highly functional. The use of Tailwind utility classes makes the layout clean, consistent, and responsive across all devices.

    🔹 What I loved:

    Responsive Design: It adapts perfectly to different screen sizes—whether you're on desktop, tablet, or mobile.

    TailwindCSS Magic: The styling is modern and easy to customize. Tailwind’s utility-first approach really shines here.

    User Experience: The dashboard is intuitive, fast-loading, and easy to navigate. All social links are neatly organized and accessible.

    Clean Code: The HTML structure is semantic and well-organized, making future enhancements a breeze.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub