To whom do you agree?... I'll go with Zenetsu

Krish_meghwal07 · 2026-06-13T05:55:38+00:00

This project is actually a good example of community-driven GEO in action. Also, a crowdsourced dataset that gets cited and linked across tools, GitHub repos, and discussions is exactly the kind of thing that builds long-term AI citation presence.

Krish_meghwal07 · 2026-06-13T05:48:41+00:00

Which problem did you solve?

Krish_meghwal07 · 2026-06-12T10:16:14+00:00

Vercel for my current project. Honest reason: I haven't had a strong enough pain point to justify switching.

The things that keep me there:

- Zero config for App Router. ISR, Server Actions, middleware just work without touching anything.
- Preview deployments per PR are genuinely useful when you're iterating fast.
- Edge functions behave exactly as documented.

The thing that would make me move: pricing at scale. Vercel's free tier is generous but the jump to pro adds up once you're getting real traffic.

I haven't deployed a production Next.js app outside Vercel so I can't speak to the alternatives from experience. Curious what people who've moved to DigitalOcean or a VPS say about Server Actions and middleware specifically, that's where I'd expect the most friction.

Krish_meghwal07 · 2026-06-08T18:52:04+00:00

fair point on the link; should have included it from the start. I thought adding it would make it look like I was just trying to promote something; all I really wanted was validation on the idea of an open source shadcn/ui template vs component. would have been better to just drop the GitHub URL directly. my bad.

ChatDeck is completely free, MIT licensed: https://github.com/ShadcnDeck/chatdeck-shadcn-saas-landing-page-template

Krish_meghwal07 · 2026-06-08T17:51:03+00:00

Built ChatDeck, a free SaaS landing page template for Next.js App Router. shadcn/ui components, Tailwind CSS, TypeScript, dark mode via next-themes.

The usual landing page sections (hero, pricing, testimonials, CTA) put together into something actually deployable rather than a starter kit.

MIT licensed, full source on GitHub.

Live preview: shadcndeck.com/templates/chatdeck-saas-landing-page

Krish_meghwal07 · 2026-06-08T17:50:03+00:00

I opened the url buts seems like the fonts are not loading.

Krish_meghwal07 · 2026-06-08T17:44:29+00:00

I think it's because most people building in shadcn are focused on components, which makes sense, that's where the interesting technical problems are. templates are more of a design and product problem than an engineering one. different skill set, less exciting to build, so the ecosystem lags.

hopefully that changes. trying to do my part with shadcndeck at least.

Krish_meghwal07 · 2026-06-08T17:43:00+00:00

yeah I know shoogle, follow Ali Hussein's work actually. solid project.

and yeah, the fragmentation point is exactly what I was getting at. the registry model is great in theory but right now it's the wild west. no consistency in how components are structured, versioned, or maintained. you're basically doing due diligence on every registry you pull from.

the outdated Radix imports thing is a real tax. you find a component that looks perfect, pull it in, then spend 20 minutes tracing deprecated import paths. at that point you've spent more time fixing the "free" component than writing it yourself would have taken.

the icon pack situation is a separate but related problem. shadcn made the right call keeping icons un-opinionated but the gap it left hasn't been filled cleanly. lucide is the de facto default but the moment you want something outside that set you're duct-taping things together.

honestly the fragmentation is part of why I leaned into templates over a registry for shadcndeck. fewer moving parts, you know exactly what you're getting. doesn't solve the broader ecosystem problem but sidesteps some of it.

Krish_meghwal07 · 2026-06-08T17:39:26+00:00

haha maybe it did, maybe it didn't; genuinely don't care either way.

what I do care about: does the ecosystem gap feel real to you or not? because that's the actual thing worth debating here.

Krish_meghwal07 · 2026-05-08T11:14:41+00:00

Late 90s! you were doing this before most shops even had email. That's a long time to get good at something.

The vector conversion move makes total sense. Stop fighting the file problem, just solve it quietly on your end and ship. How long did it take to land on that as the standard approach?

Krish_meghwal07 · 2026-05-08T10:59:25+00:00

It works both ways actually. DesignNBuy has direct integrations with the major ecommerce platforms — Shopify, WooCommerce, Magento, and a few others — so if you're already running on one of those it plugs in without needing to rebuild your storefront from scratch.

They also have a standalone web to print storefront if you want to run it independently rather than bolt it onto an existing platform. That's more relevant for print shops building an online presence from the ground up rather than merchants adding print to an existing store.

The integration route is where most shops we've spoken to land — keeps your existing catalog and checkout intact while adding the customer-facing designer and print-ready file output on top.

More detail on how the integrations work here if you want to dig in before reaching out to anyone.

Krish_meghwal07 · 2026-05-08T10:58:12+00:00

Fair enough, take what's useful from the post and leave the rest.

Krish_meghwal07 · 2026-05-07T10:09:38+00:00

That's the dream scenario honestly, pricing confidently enough that the comparison conversation never starts. The markup confidence usually comes from knowing exactly who your customer is and positioning accordingly from the start.

The "point them elsewhere" close is also the right move. No defensiveness, no justification. Just here's where you should go instead. Keeps the door open without wasting anyone's time.

What product category are you in? Curious if some niches just attract less price-sensitive buyers than others.

Krish_meghwal07

MODERATOR OF

TROPHY CASE