Design comparison
Solution retrospective
This was my first time using tailwind and while it was hard to get used to, I'm proud of how quickly I adapted to it. I'd actually include tailwind in my project next time instead of simply getting the link for the site as I did this for easiness here.
What challenges did you encounter, and how did you overcome them?Mainly just getting used to tailwind and also trying to get my margin/padding as close as possible to the design given.
What specific areas of your project would you like help with?Is it normal in tailwind to just have multiple classes that are the exact same? This doesn't seem efficient. I also think I was too precise with my margins here and it feels like there was a better way to do this.
Community feedback
- @R3ygoskiPosted 7 months ago
Hello Lyle.
Answering your question about Tailwind CSS, it's correct. I believe you might have been confused about the correct use of
margin, right? Well, they are correct, don't worry, there were no major redundancies.A tip about your semantics, it's almost impeccable, there's just a small issue, which was the excessive use of
<section>, I'm referring to the part with the buttons. The most correct thing would be for them to be<a>instead of<section>, because they are actually links. And if you want to change them to<a>, I recommend also changing the<section>on line 39 to a<ul>and<li>.That's all for now, congratulations, keep practicing and improving, you're doing well. If you have any questions, you know what to do, just comment below.
Marked as helpful1@Squing0Posted 7 months agoThanks for your feedback. Using a unordered list with list items and links is definitely more semantic and makes more sense here.@R3ygoski
1
Please log in to post a comment
Log in with GitHub
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