Tailwind css, vite, Vue

Solution retrospective
I am most proud of trying out the combination of Vite, Vue, and Tailwind CSS. I am more familiar with the Next.js, React, and module.css workflow. Next time, I might stick to the combination of Next.js, React, and module.css but integrate Tailwind CSS as well. This is because I spent too much time exploring new tools, and I think I should focus on mastering one setup first.
What challenges did you encounter, and how did you overcome them?I learned how to use Vue's v-for
, which works similarly to React's map
, to render ref()
data. I also practiced using the :class
binding syntax to implement conditional rendering. Additionally, I discovered and understood more Tailwind CSS shorthand utilities.
Most of the time, my challenges come from unfamiliar syntax, but I can usually find solutions by referring to documentation. However, I encountered an issue during deployment: image paths that worked locally couldn’t be found after deployment. I resolved this by moving the images from /src/asset/image
to the /public
folder, but I’m not sure why this happened.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on yyuntzpan'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