Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
26
Comments
13

Dipesh

@Dipesh-sapkota1Kathmandu430 points

I’m a mysterious individual who has yet to fill out my bio. One thing’s for certain: I love writing front-end code!

Latest solutions

  • tip calculator using tailwindcss


    Dipesh•430
    Submitted 11 months ago

    1 comment
  • responsive time-tracking-dashboard using tailwindcss

    #tailwind-css

    Dipesh•430
    Submitted 11 months ago

    1 comment
  • social-links-profile-using-tailwindcss

    #tailwind-css

    Dipesh•430
    Submitted 11 months ago

    I want to know how professionally maintain and deploy my project. I want to know the process of continuous integration.


    0 comments
  • recipe-page-main


    Dipesh•430
    Submitted 12 months ago

    1 comment
  • responsive blog-preview-card-main


    Dipesh•430
    Submitted 12 months ago

    1 comment
  • responsive newsletter form using flex-box


    Dipesh•430
    Submitted 12 months ago

    I want to improve responsiveness of overall site.


    1 comment
View more solutions

Latest comments

  • Josephine Fitalvo•260
    @fitalvojosephine
    Submitted 11 months ago
    What are you most proud of, and what would you do differently next time?

    I am proud that I finally finished this challenge. Next time, I will do more research and dig deeper into learning the structure of the DOM, validation, and submission. Honestly, this is where I got stuck. But with the help of YouTube and ChatGPT, I made it. Thank you, Google, YouTube, and ChatGPT.

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

    First, I encountered challenges in the layout and figuring out how to structure my HTML and CSS to implement the DOM. So, I researched it, read some other developers' code, and tried applying it to my own code, eventually finding my own way. I am happy that I overcame it all, including mobile responsiveness, which I managed with the help of reading documentation and implementing it in my CSS code.

    The hardest part was the JS fundamentals of form validation. I researched it to understand how it works, including the functionality of addEventListener, using if statements for error messages, displaying elements using the DOM, toggling state to hide the form, and the regex for invalid email validation. This was really challenging, but I had fun and didn't give up. I must learn more and apply this knowledge to other challenging projects.

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

    So far none. #HappyCodingEveryone

    Newsletter sign-up form with success message using HTML, CSS, JS.

    #bem
    1
    Dipesh•430
    @Dipesh-sapkota1
    Posted 11 months ago

    Congratulation on completion of your project

  • Branka R•290
    @brainka
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    Pretty happy with how I approached this and managed to get the responsive layout to work on multiple devices.

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

    Many!

    Getting used to adding multiple event listeners for different requirements aka click, input, keypress.

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

    None at the moment!

    Thank you

    Reponsive Tip Calculator App

    1
    Dipesh•430
    @Dipesh-sapkota1
    Posted 11 months ago

    Congratulation on completing tip-calculator Everything looks great but your form is overflowing vertically, try using logical units for layouts

  • Tobias Davies•10
    @PROJECT-POWERJMC
    Submitted 11 months ago

    Recipe with HTML and CSS

    1
    Dipesh•430
    @Dipesh-sapkota1
    Posted 11 months ago

    Try using container to limit your content

  • qvazi•100
    @qvazi
    Submitted 11 months ago
    What challenges did you encounter, and how did you overcome them?

    no figma

    next tailwind

    #next#tailwind-css#react
    1
    Dipesh•430
    @Dipesh-sapkota1
    Posted 11 months ago

    Awesome work

  • 7A9Oo•80
    @7A9Oo
    Submitted 11 months ago
    What are you most proud of, and what would you do differently next time?

    To use variables for the CSS style and selector like first of type . I learned to effectively use CSS custom properties (variables) to manage design attributes more efficiently. creating preset font and use them as class.

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

    Working with media queries

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

    working on mobile media queries first or on desktop

    blog view card using preset font

    2
    Dipesh•430
    @Dipesh-sapkota1
    Posted 11 months ago

    You did good

  • Rebeka•170
    @BekiaD
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    The layout and the animations. Little details like hover states.

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

    The refactoring of the JS into for loops was a bit mind boggling. I find it difficult to think through the process so I use mindmaps for this. Deploying the tailwind project to netlify also took quite some time to figure out

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

    Any feedback is welcome.

    • on mobile view the top part of the card is cut off because of the h-screen, but if i change it to sm:h-screen it looks fine on mobile, but not aligned on desktop view
    • There is a part commented out in my code that would pop up a share button when hovered over the ellipses (...) at each card. I found here difficult to work with the cards individually with a lot of repetition.
    • Also the bigger issue is that after the mouseover event the popup stays there.

    Tailwind CSS Time Tracking Dashboard

    #tailwind-css
    1
    Dipesh•430
    @Dipesh-sapkota1
    Posted 11 months ago

    🎉Congratulation on completion of your project🎉

    1.Card Overflow and Layout: -To prevent card overflow issues, consider using min-h-screen. Browsers naturally try to preserve content, and issues often arise from unnecessary CSS. Your layout breaks at the small break-point because the required columns were not specified to fit all the cards. Ensure that your grid system accommodates all elements at different breakpoints.

    2.Netlify Deployment: -Great job attempting to deploy on Netlify! However, I couldn't view your website. When deploying with frameworks or libraries, make sure to specify the base directory and build command. This extra step is crucial for successful deployment.

    3.JavaScript Improvements: -Your JavaScript is currently not working. Here are a few suggestions: Use querySelectorAll for selecting multiple elements and adding event listeners. Break down large functions into smaller, reusable, and manageable functions.

    4.Design Focus: -Being creative is fantastic, but make sure to focus on basic design principles first. This will ensure a solid foundation before adding more creative elements.

View more comments
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