Personal blog - Next.js 15 | Tailwind CSS 4 | shadcn/ui

Solution retrospective
I was a pure CSS or die kind of guy. I'm proud of trying tailwindcss, I really liked it and with shadcn it just got easier to build the design system and the theme switch. This will be my standard from now on. Next time I would set properly better @utility
and @components
classes in tailwind.
Learning tailwindcss principles and setting up the themes and knowing the purpose for each css variable. Once I understood that, the theming was easier, since almost everything was changed in the globals.css
for once and there were a few exceptions that I had to specify for dark mode for specific components.
Any feedback is welcome. This project was to try different stuff and make it a fullstack app, like using the built-in Next.js API routes to handle the backend server, authentication (for a future blog manager inside this project), fetching posts from a database, using an ORM, it was a while since I don't do much backend stuff and this was a nice refresher.
Think I could get suggestions on how to implement i18n. My mother language is Spanish (Mexico), and since I'm going to be actually using this page, I would like to have support for English and an additional button (like the theme switcher) to select between different languages.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Juan Daniel Martínez'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