dub VS taxonomy

Github Repository: Here

Dub An open-source link management tool for modern marketing teams to create, share, and track short links Introduction · Features · Tech Stack · Self-hosting · Contributing Introduction Dub.co is the open-source link management infrastructure for modern marketing teams. Features Advanced Analytics Branded Links QR Codes Personalization Team Collaboration Tech Stack Next.js – framework TypeScript – language Tailwind – CSS Upstash – redis Tinybird – analytics PlanetScale – database NextAuth.js – auth BoxyHQ – SSO/SAML Turborepo – monorepo Stripe – payments Postmark – emails Vercel – deployments Self-Hosting You can self-host Dub.co for greater control over your data and design. Read this guide to learn more. Contributing We love our contributors! Here's how you can contribute: Open an issue if you believe you've encountered a bug. Follow the local development guide to get your local dev environment set up. Make a pull request to add new features/make quality-of-life improvements/fix bugs. …

Thank you so much for reading to the end. Of all the tools on this site, Penpot is my absolute favorite. Its modern UI and all the amazing tools at the cost of running a single docker command is a real catch! As a thank you, there's another tool I'd like to present. It's called Dub. It's a link-shortener tool with lots of advanced features for marketing teams and a perfect addition for Umami.

Dub - Open Source Alternative to Bitly

GitHub: https://github.com/steven-tey/dub

dub.sh - with redirection Redirects to app.dub.sh when you try to login github repo shows the app. in the app/ router, and domain in the [dub.sh] folder

There are amazing open-source projects to learn from. Few are: - cal.com - dub.sh - highstorm.app

Very cool stuff, thanks for open-sourcing this! Might incorporate it into Dub , an open-source link management tool that I'm building: https://github.com/steven-tey/dub

I am building this app with inspiration from Taxonomy and Acme corp so a lot of the design comes from there.

View on GitHub

Now, I must confess that I'm primarily a back-end engineer, and crafting a beautiful front-end was, well, a bit of an adventure. To keep things straightforward, I opted for simplicity. I figured I could enhance it as my customer base grew, as the real value, of course, lies in the robustness of the API and its backend. Looking back, I might consider using a template like https://tx.shadcn.com/ if I were to start all over again. It appears to be a great starting point for any SaaS, but the setup might pose some challenges.

Check out these two GitHub repositories: https://github.com/sadmann7/skateshop/ and https://github.com/shadcn/taxonomy/. They both use Next.js 13 and have well-structured folders and well-written code. Next.js provides performance optimization. To improve it further, avoid loading unnecessary items and use a CDN for fast content delivery. Both not loading unnecessary content & lazy loading) and CDN is 2 individual topics to dive into.

I've also been inspired by this repo, but the Vercel template seems more achievable for me at this point.

In addition to the repository I mentioned in my original post, I've also been inspired by another repository (Taxonomy Repo) which has implemented a similar Stripe integration. However, this one is a bit more complex and I'm finding the Vercel template to be more achievable for my current skill level.

I'm currently working on a Next.js project where I'm trying to integrate Stripe for payments and webhooks. I've been following the Taxonomy GitHub repo for guidance, particularly for setting up the app router and the lib files.