@mkborisSubmitted 7 months ago
KrishnaPoddar1
@KrishnaPoddar1All comments
- @KrishnaPoddar1Posted 5 months ago
Everything looks good. The Navbar can be adjusted a little to go on top and can be made fixed to make sure that it remains at the top all the times.
0 - @kaoutar-ouadihSubmitted 5 months agoWhat are you most proud of, and what would you do differently next time?
I'm proud of completing this challenge!
What challenges did you encounter, and how did you overcome them?.
What specific areas of your project would you like help with?Anything that can help me improve.
- @TorHammSubmitted 6 months agoWhat are you most proud of, and what would you do differently next time?
try make it more accessible
What challenges did you encounter, and how did you overcome them?open for any suggestion
@KrishnaPoddar1Posted 5 months agoThe code looks clean. The only suggestion I can give is usage of <section> instead of <div>
0 - @coder-abdoSubmitted 5 months agoWhat are you most proud of, and what would you do differently next time?
Adding accessibility and semantic HTML5 is what I am most proud of. I can submit another solution using
What challenges did you encounter, and how did you overcome them?Reactandtailwindcss.there are no tough challenges that I face in this challenge but I have a little challenge which is adding an active state and removing from other children I searched a lot and finally, I found the solution in the
What specific areas of your project would you like help with?poe.com.I think I covered the most areas in that challenge, so I can't think of any places where I need help.
@KrishnaPoddar1Posted 5 months agoHey @coder-abdo . I went through your solution and i think you can Improve the accessibility by using <section> instead of <div>. Along with that i think it will be better to add the relative path to your files rather than absolute one's Eg:
Marked as helpful0 - @wiiggyyySubmitted 9 months ago@KrishnaPoddar1Posted 7 months ago
The total tip value calculated is wrong as the tip is not being added. The container is breaking when I'm in 100% zoom in both the mobile-view and desktop-view (The elements are coming out of the form element).
I think it can be solved by having the form element inside a container and giving that a height. I'm not sure so you'll have to check it out
0 - @matbac85Submitted 7 months agoWhat are you most proud of, and what would you do differently next time?
I'm happy to be making gradual progress in learning JavaScript, even if I'm still getting stuck on some simple elements.
What challenges did you encounter, and how did you overcome them?The most difficult part for me was displaying the timeframes according to the button clicked (monthly, weekly or daily).
I've created a specific function for this.
What specific areas of your project would you like help with?I can't see anything at the moment, but if you have any comments, I'd love to hear from you.
@KrishnaPoddar1Posted 7 months agoHey your solution was really helpful. Helped me solve an issue which i had encountered while solving my solution. Thank you!!
0 - @AlfredoPegueroCSubmitted 10 months ago@KrishnaPoddar1Posted 7 months ago
Your Code seems good("I don't know a lot about JSON")
can you look at my code and tell me why its not working(I had to use brute force to make it work in nextFunc()). [URL] (https://github.com/KrishnaPoddar1/TimeTrackingDashboard.git) Live Site
0 - @ba311Submitted 8 months ago@KrishnaPoddar1Posted 7 months ago
When that thank you card is loaded you can give the value of the email in the <b id=mail> element. That will make it customized for every user.
Marked as helpful0 - @KevinBlyweertSubmitted 7 months agoWhat are you most proud of, and what would you do differently next time?
None
What challenges did you encounter, and how did you overcome them?None
What specific areas of your project would you like help with?None
@KrishnaPoddar1Posted 7 months agoThe JS Code in my file is not working as it should. It does work at time and doesn't work at all at times. Can you look into it and let me know what's wrong? Link to the GitHub Repo: https://github.com/KrishnaPoddar1/ArtcilePreviewComponent.git
Any Advice/Tips/Suggestions will be welcomed!!
Thank you!
0 - @CropsiiSubmitted 8 months agoWhat are you most proud of, and what would you do differently next time?
Изучил как работает grid и разобрался с grid-area
What challenges did you encounter, and how did you overcome them?Долго сидел с позиционированием имени и лого, также была затупка с grid-area
What specific areas of your project would you like help with?У меня текст в последней колоне странно спозиционирован, хотел бы узнать как это поправить
@KrishnaPoddar1Posted 8 months agoLooks good and simple but i think it will be helpful if you use semantic tags
0 - @DAEM007Submitted 8 months agoWhat are you most proud of, and what would you do differently next time?
- I am happy I had to work with vanilla css to create the responsive design of this feature.
- The little challenge was just trying to make the cards look good on most screens. I had to employ flexbox along with little media queries.
- I am opened to ideas on how I can improve the implementation of my solution.
@KrishnaPoddar1Posted 8 months agoI think there was no need to put up a display: flex in the card class and middle-card class. I maybe wrong but do let me know.
0 - @fariidlotfiSubmitted 8 months agoWhat are you most proud of, and what would you do differently next time?
creating layouts is most important tasks in any websites. in the future i use some other techniques like grid.
What challenges did you encounter, and how did you overcome them?nothing important
What specific areas of your project would you like help with?nothing. because i have some experiences and coding for less than one year and is easy for me
@KrishnaPoddar1Posted 8 months agoThe mobile view can be refined by reducing the width in the .box.
Try using the em or rem units for sizing as they change based on the size of the window.
0
