Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 14 days ago

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

next, prisma, shadcn, supabase, tailwind-css
Juan Daniel Martínez•500
@juandadev
A solution to the Personal blog challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

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.

What challenges did you encounter, and how did you overcome them?

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.

What specific areas of your project would you like help with?

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.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community 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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.