@giuseppe-giannottaSubmitted 8 days ago
Latest comments
- P@Stash443Posted 5 days ago
Hi there, the code doesn't look finished. It didn't include semantic HTML. I'm not sure if naming a css file an index is fine but i think its better if you name your css files as styles.css instead of index.css and try using Grid to center your parent container. but overall nice try though.
Marked as helpful0 - @isaiahp04Submitted 6 days agoP@Stash443Posted 6 days ago
Your code has semantic HTML which is good. The code is well structured and readable. You also added comments on the code so that the next person can understand. Although I do recommend you use rem units for font size's of text, it helps a lot with responsive layouts. Well done.
0 - @MustafizaliSubmitted 11 days agoP@Stash443Posted 10 days ago
The code is readable but you didn't include semantic HTML. The layout looks the same as the design. Well done.
0 - @zardrickSubmitted 15 days agoWhat are you most proud of, and what would you do differently next time?
I’m proud of how well the layout and typography turned out, especially the clean and structured design. The use of CSS custom properties and responsive styling made the page look great on different screen sizes.
What challenges did you encounter, and how did you overcome them?Handling the list styling for the ingredients and preparation steps required tweaking the default styles. I used CSS pseudo-elements to customize bullet points and markers, achieving a cleaner, more polished look.
What specific areas of your project would you like help with?I’d love feedback on: Code Structure: Are my CSS and HTML well-organized? Best Practices: Any unnecessary code or areas for improvement?
P@Stash443Posted 14 days agoYour solution does not contain semantic HTML, try implementing it in future projects it helps with SEO and readability. Also normalize adding comments in your CSS so that you don't get confused next time you view your code after a while. Your code is well structured and readable as well as your media query. Overall you have coded well. Well done.
0 - @doganayurgupluogluSubmitted 18 days agoWhat challenges did you encounter, and how did you overcome them?
It could probably have been coded in a more optimized way, but I wanted everything to be contained within a single container. If there are any mistakes you would like to correct or improvements you would like to suggest, please feel free to provide feedback.
P@Stash443Posted 18 days agoThe code is well structured and readable. Although I've noticed that your solution code didn't include responsive code for mobile screens but all in all it's similar to the design, there's just a slight width difference. Well done.
Marked as helpful1 - @subjectiverealityySubmitted 20 days agoWhat challenges did you encounter, and how did you overcome them?
When I was pushing to Git, I kept making mistakes on the README.md file and had to keep repeating the process of git add, git commit and git push. I have now gotten it to read the way I want it to. The problems originated from using the wrong file paths for the README.md file and my project's screenshot initially.
P@Stash443Posted 19 days agoThe solution was well built, as well as the responsive(media query) part was well structured and understandable. I don't see any improvements that need to be implemented here. Well done.
1
