Single Price Component: Joining Has Never Been Easier

Solution retrospective
I take pride in using the Tailwind framework for this project. Initially, I had doubts about its complexity, but it turned out to be a powerful and enjoyable tool. For future projects, I would delve deeper into exploring the classes offered by Tailwind.
What challenges did you encounter, and how did you overcome them?Transitioning from pure CSS to Tailwind was a significant change. While I knew some CSS properties, adapting to Tailwind's syntax was a challenge. I researched the documentation and successfully tackled this obstacle. Although I'm not a fan of inline styles, I appreciate not having to worry about class naming, which has sometimes been my weak point.
What specific areas of your project would you like help with?- Regarding design, I noticed a "button" with the text "Sign Up." My question is whether I used the correct element. Should I have used an anchor (
) or a button ()? - Additionally, is there a recommended folder or file structure for organizing CSS styles, such as naming conventions for
input.cssoroutput.css?
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on alchrdev's solution.
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