taxonomy VS cal.com

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.

Cal.com is an open-source event-juggling scheduler for everyone, and is free for individuals.

Turborepo is a tool that makes it easy to manage monorepos with pnpm and typescript. On large open source porject like cal.com they use it for fast building or running developing tasks like testing or linting. Turborepo depend havily on caching so it would reduce signficantly the time to build or run the tasks as well as CI/CD pipelines time and cost.

The next codebase to analyse is cal.com. This repo is larger than jsoncrack. It is a monorepo with packages and lots of stuff going behind the scenes.

hey, peer here from cal.com. we have an issue where we track all individual caldav implementations: https://github.com/calcom/cal.com/issues/9990

Cal - Alternative to Calendly

I force clients who want to talk to me to book a call. I use cal.com (free) and my Google Calendar (which its linked to) only allows calls on specific days/times. I have a few "Call Blocks" where they can book. That let's me do calls in a small section of my week, with ample downtime to recover the rest of the week. I'm still learning how many calls a day I can handle. Currently anything more than 2 is too much.

Cal.com- Cal.com is a scheduling tool that helps you schedule meetings without the back-and-forth emails.

Peer Rich (CEO at Cal.com)

Has any one deployed cal.com with selfhosted environment. Is yes how would have configured prisma for the same.

Recently I came across a company called cal.com, it's a Calendly alternative, but the catch is the entire software is open source: https://github.com/calcom/cal.com.