taxonomy VS n8n

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.

I believe you can achieve that with n8n. Used in past (and still running) for some data transformation and little more. Possibly similar case what are you describing.

https://n8n.io/

A startup, "DevOps Solutions" adopts Helm to streamline their Kubernetes deployments. You're a consultant tasked with creating a basic Helm Chart for n8n. It should be customizable for different environments using values.

n8n.io - a powerful workflow automation tool

N8N - Open Source Alternative to Zapier

N8N - anything that I would have used Zapier or IFTTT for I now use N8N. It is a bit harder to use but more powerful.

I'm using Weweb as my front end and Supabase as my back end. I'm also looking into n8n.io to run some of the backend logic that I'm either unsure how to code myself within Supabase or unsure if Supabase can perform those back-end tasks and workflows. Curious what stack or tools other Supabase users are using?

This is similar to something I saw before: https://n8n.io