@MikDra1Submitted 3 months ago
Nathan Orobor
@omarnate1All comments
- @ThiagouhSubmitted 4 months agoWhat are you most proud of, and what would you do differently next time?
I better understood the use of Grid and I intend to continue using it to understand more.
What challenges did you encounter, and how did you overcome them?my problem was dealing with the inversion of positions of some cards present, but I managed to solve it by persisting.
What specific areas of your project would you like help with?Any feedback on the project is welcome!
@omarnate1Posted 4 months agovery nice work, comparing it with the original design, you can make some adjustments to position it at the center.
0 - @DearNatthaphongSubmitted 6 months agoWhat are you most proud of, and what would you do differently next time?
Having issues with drop-shadow in Tailwind CSS. Welcome to any suggestions.
What challenges did you encounter, and how did you overcome them?Having issues with drop-shadow in Tailwind CSS. Welcome to any suggestions.
What specific areas of your project would you like help with?Having issues with drop-shadow in Tailwind CSS. Welcome to any suggestions.
@omarnate1Posted 4 months agoclean work mate, keep it up
next time try and spare a few minutes to edit the readme-template and readme files to have your details.
overall, job well done.
0 - @Smart-Ace-DesignsSubmitted 5 months agoWhat are you most proud of, and what would you do differently next time?
Learning new CSS tricks such as adding spacing between letters and adjusting line height. What I would do differently is handle the dual image differently. I believe the solution is to use the element, but I could not figure out how to map its functionality to the Astro equivalent - so I used the "hidden" declaration instead which is not ideal.
What challenges did you encounter, and how did you overcome them?Spend way too much time tweaking spacing, text size, text weight, etc. Perhaps Figma might help.
What specific areas of your project would you like help with?Using the Astro component to select different images based on the screen size. The documentation, that I found, does not seem to explain how to do this (assuming it is even possible to do with this component).
- @jamesbrown173Submitted 4 months ago@omarnate1Posted 4 months ago
Nice work, but take a little time to edit your README.md to have your details. I looked at your codes and the README.md files and template are all the same.
Marked as helpful0 - @omarnate1Submitted 5 months agoWhat are you most proud of, and what would you do differently next time?
nothing new
What challenges did you encounter, and how did you overcome them?none
What specific areas of your project would you like help with?none
@omarnate1Posted 4 months agoThe solution includes semantic HTML with correct usage of elements like <header>, <main>, <footer>, and <nav>.
To improve, verify that semantic elements are used where applicable, such as <article> for independent content sections.
For accessibility, check for ARIA roles, alt attributes on images, and proper labeling of form elements.
Use landmarks to improve navigation for screen readers and ensure sufficient color contrast. The layout uses responsive units and media queries effectively.
0 - @yousef89Submitted 4 months ago
- @yousef89Submitted 4 months ago
- @dsaneshaikhSubmitted 4 months ago@omarnate1Posted 4 months ago
- Semantic HTML: The solution effectively uses semantic HTML, enhancing both structure and accessibility.
- Accessibility: The design is accessible, with clear improvements made for screen readers.
- Responsive Layout: The layout is responsive, and looks great on various screen sizes.
- Code Quality: The code is well-structured, readable, and highly reusable.
- Design Adherence: The solution closely follows the original design, ensuring visual consistency.
0
