@KuzukaniSubmitted 4 days ago
What specific areas of your project would you like help with?
i have issue here that when it come to dark theme. i dont know how to make logo text become white. appreciate the answer
Latest solutions
Interactive comments section
#react#vite#tailwind-cssSubmitted 27 days agoAny feedback especially regarding how nested my code is and excessive prop drilling. Any recommendations on building this into a full stack app.
Product list with cart
#react#tailwind-css#viteSubmitted about 2 months agoAny feedback is appreciated, particually a way to keep the cart in a fixed position when scrolling down with overflow on tablet and desktop viewports.
Conference ticket generator
#framer-motion#react#vite#tailwind-cssSubmitted 3 months agoAny feedback is appreciated.
Rock paper scissors
#react#tailwind-css#vite#framer-motionSubmitted 5 months agoany feedback is appreciated.
Latest comments
- @jjdavenportPosted 4 days ago
My approach is to edit the code of the SVG itself , that particular svg has two <path> elements to change the color you need to change the fill="" for dark mode.
0 - @jjdavenportSubmitted 5 months agoWhat are you most proud of, and what would you do differently next time?
Learning react router to route to different pages and keyframes animation on the destinations page.
What challenges did you encounter, and how did you overcome them?The only challenge was the image sizing on tablet and desktop.
What specific areas of your project would you like help with?Any solution to having the images fixed to the bottom of the page would be helpful.
@jjdavenportPosted 2 months agoThanks for the feedback, I'm going to look into that and update the repo.
0 - @AyodelearogSubmitted 3 months agoWhat are you most proud of, and what would you do differently next time?
It definitely chhallenged me, but I'm gald I pulled through and did something I can be proud of.
What challenges did you encounter, and how did you overcome them?I struggled somewhat with the fonts. I kept on encountering a bug that meant that some texts are not displaying as they should. But I managed to make it work by specifying the font size carefully to avoid contradictions.
What specific areas of your project would you like help with?I just need constructive criticism and a job if possible.
@jjdavenportPosted 3 months agoThe solution includes semantic html , the code is well structured and readable , the site looks great on desktop and mobile , the only issue with mobile is the page titles text being a little too large. On tablet the issue is the nav not being on the right hand side of the page. The solution is great just needs a few fixes, like the desktop solution starting from 1500px instead of 1000px and the size of the text titles on mobile.
well done.
0 - @JEJS-IA97Submitted 6 months ago@jjdavenportPosted 6 months ago
The solution does include some semantic html, could be improved with footer, and section elements, but lacks accessibility because all the buttons are divs. The layout looks best on desktop however on mobile suffers from compression on smaller screens and does not match the design because main does not fill the width of the viewport. The calculator itself does work sometimes but has lots of bugs, the main bug being that the reset div does not reset the button divs and when a button div is selected there can be an input in the custom input at the same time as a button being selected.
Marked as helpful0 - @sksksk2024Submitted 7 months agoWhat are you most proud of, and what would you do differently next time?
Definetily I'll do this one in React, TypeScript with Vite and Vitest next time!!! And other than that, I'll be focusing on resolving the JS problem(where in the add ons section, when you select yearly payment, you should see yearly prices, not monthly or incorect calcs)
What specific areas of your project would you like help with?Any ideas to show properly the add-ons when is yearly(not showing as expected) is welcome!
@jjdavenportPosted 7 months agoThe path to your images is wrong, should be "./assets/images/img".
1 - @saifuldtSubmitted 9 months ago@jjdavenportPosted 8 months ago
The site does use semantic html, however the mobile menu is in a <div> and should be a <dialog>. The basic layout of the page is correct on desktop, however some of the content is contained in the wrong elements leading to one of the <img> backgrounds being in the wrong place. The mobile viewport is much worse with significant overflow issues due to some the elements having a fixed width.
0
