Meet Landing Page: React + TailwindCSS

Solution retrospective
I was able to troubleshoot most of the issues by just trying things out. I would look it up immediately (on google or the documentation) but I want to push my mind into figuring things out myself first to retain the knowledge better.
What challenges did you encounter, and how did you overcome them?First was the footer image absolute beneath a transparent background, then the hero image (I didn't notice the images for the tablet and desktop were different until I had completed the project). It was a combination of relearning the css property's structure and patience.
What specific areas of your project would you like help with?I have noticed in most of my projects that I tend to put everything in a div immediately and give it the tailwind property of min-h-screen
to take on the full height of the viewport. Is that recommended or is there a better standard of doing it?
Please log in to post a comment
Log in with GitHubCommunity feedback
- @MarziaJalili
An absolute masterpiece! 🎉
🌟 About semantics?
✅ Make the <div> element you very last choice, bro, as it doesn't give enough info to the screen readers. Instead try to come up with those fancy shmancy HTML elements.
✨ While your code is flawless, but here's what you can change:
- Use the <section> element for all of the different sections. Like the photos, for example.
🔥 Great work overall, keep it up!
Marked as helpful
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord