wrote tailwind for the first time, most stressful project in all my learnings haha. But i overcame!
What challenges did you encounter, and how did you overcome them?first time writing tailwind. persevered and conquered
Some design adjustments are needed. There should be a cursor pointer when hovering over the navigation sections in the navbar. Transition speed is too slow.
dfsd
What challenges did you encounter, and how did you overcome them?sdfsd
What specific areas of your project would you like help with?sdfsd
A gradient black layer could be added from bottom to top to make the text on the photos more readable.
Fairly happy with this project.
I may swap the tip amount radio buttons for regular buttons, it would be helpful to deselect a tip amount directly if required.
I am proud of keeping things simple. It works, and I believe I will be able to understand the code even if I return to it far in the future. React and Tailwind CSS make the code easy to plug in and port to other projects.
The codes are divided into groups according to their content. The readability of the code is good. Responsive design applied
I'm most proud of successfully deploying my TailwindCSS project to Netlify, achieving a smooth user experience with fast load times and responsive design. Integrating TailwindCSS, configuring the build process, and effectively using Git and GitHub for version control and continuous deployment were significant accomplishments. These steps ensured the project was always up-to-date and that any changes were automatically deployed.
Next time, I would implement more comprehensive testing for different devices and screen sizes to ensure consistent responsiveness. I would also focus on improving documentation, error handling, and performance optimization, such as lazy loading images and reducing bundle sizes. Additionally, setting up advanced CI/CD pipelines and establishing a user feedback loop would help in making iterative improvements and ensuring a smoother user experience.
I feel happy with the learning process; in a way, following the learning path has helped me a lot.
Very well-written, well-organized and readable code. The design is close to the original. It is responsive and has a good mobile appearance.
Responsive design for small, medium and large screens. The design looks nice
I am most proud of using the picture and source tags to make the image responsive and change based on the size of the screen. I have never used those tags before, so it was cool learning about and using them. I normally would have used React state to control which image shows, but I wanted to try something different and am happy with the outcome.
I am still learning how to use styled-components, so before this I did not know how to create default styles and global styles. I was able to learn how to create them by reviewing another user's code and implementing their technique in my own code. I made sure to take my time and try to understand each part, so I will be able to fully understand in future projects.
I am most proud of my continued use of styled components. I felt like I could have made the code better by making the component reusable (i.e. passing data as props so the component could be used with other recipes) and would do that differently next time.
What specific areas of your project would you like help with?I'm still not sure if I should be using styled-components for all of my components. I think it looks cleaner on the component page side, but feels strange having some styled-components without styles. I would like advice from a more experienced styled-component user.
