A complete & open-source Next.js 14 Subscription Starter template using Supabase, Stripe. Clean blogs and docs using Fumadocs (mdx compiler). Complete Landing page using Tailwind CSS, ShadcnUI, and Magic UI.
No reviews yetBe the first to leave a review for Hikari
Maker
๐
The inspiration for this project is Taxonomy, which is a modern starter template for Nextjs.13. Initially, I used Taxonomy as a way to understand Next.js โ I loved how the design was simple and clean. After using Taxonomy for a while, I discovered it lacked certain features and the level of customization I desired. For instance:
1. Documentation: Contentlayer, which was a crucial component for building a documentation site, was no longer supported in Next.js 14.
2. Authentication: Clerk was an easy authentication system, but I preferred Supabase for its flexibility and ease of use. While there was a Supabase version of Taxonomy, its authentication logic differed from my preferred implementation.
3. Database: I also preferred using Supabase Postgres over Planetscale or Prisma for database management.
โ
I often found myself returning to the Supabase subscription repository as a starting point, customizing it to include components from Taxonomy. This repetitive process made me realize the need for a more tailored solution.
And that's how the baby Hikari was born.
Building Hikari wasn't just about solving my own problems. I'm a firm believer in open source and wanted to give back to the community that has helped me learn and grow. By sharing Hikari, I hope to contribute to the ecosystem and help other developers who might face similar challenges.
Please let me know how it helps you in your developer journey!
Report
Hikari sounds like a game-changer! ๐ Love how you mixed Supabase, Stripe, and that sleek Tailwind design. Itโs always refreshing to see a project build off a solid foundation like Taxonomy but add that personal touch based on real needs. Documentation can truly make or break a project, so Fumadocs sounds like a smart choice. Canโt wait to see how this evolves and supports more devs on their journeys. Keep up the great work, @antoineross! Curious if you have plans for any specific features or integrations down the line?
Report
Maker
hi @ezshine,
thanks for the kind words. I have plans set up for newer features but it's not a priority until many people request it.
the roadmap for now is just :
- update it when newer versions of APIs come out
- i18n. i'm looking for a better way to do it still, I don't personally prefer calling const foo = t'foo', for all of my components. especially ugly to implement with clients
- anything the community wants if they give feedback, I don't really get any of that yet. I opened a discussions tab on Github so if anyone wants to chip in here is the link: https://github.com/antoineross/H...