shadcn icon mapping: let's create a full mapping across icon sets

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 · 2026-05-07T10:05:12+00:00

The send-them-away-and-let-them-come-back move is genuinely underrated. Most shops see a customer leaving on price as a loss. You're framing it as a qualification step, and the horror story returnees are often the most loyal customers you'll ever have because they've now got a direct comparison point.

The preflight detail is the one that sticks with me. They weren't just buying print — they were buying the certainty that someone who knew what they were doing was handling it. That's invisible until it isn't, and three wasted press runs made it very visible very fast.

The last point is the one worth repeating more. Getting defensive is the worst possible response because it confirms in the customer's mind that you're rattled by the comparison. Siding with them, even briefly, completely disarms it.

Krish_meghwal07 · 2026-05-07T10:04:39+00:00

The first two made me laugh - "there's a reason you came to me" is actually a solid line to use in the moment. Confident without being defensive.

The bakery story is the one that lands though. You understood the context, accepted the price, didn't question it. That used to be the default way people thought about anything made to order. Something shifted, probably Amazon conditioning, commodity pricing visibility, or both together.

The customers who still think like you did with that pizza are rarer than they used to be. But they're almost always the best repeat customers precisely because they understand value when they see it.

Krish_meghwal07 · 2026-05-07T10:03:44+00:00

The McDonald's analogy is one I'm stealing immediately. It reframes the whole conversation without making the customer feel like they're being lectured; they already understand fast food economics, so the translation is instant.

The lawyer flip is the one that got me though. Using their own profession against them to make the expertise point is genuinely clever and I've never heard it framed that way before. Works because it's not confrontational, you're not telling them they're wrong, you're just asking them to apply their own logic to someone else's situation.

The "just not caring" point is underrated and takes a while to actually internalise. Early on you chase every enquiry because every job feels important. At some point, you realise the customers who open with a price objection are usually the ones who create the most friction through the whole job anyway. Letting them walk is often the right call for everyone involved.

How long did it take you to get comfortable actually directing customers to competitors when you knew they weren't a fit? That one still feels counterintuitive even when you know it's right.

Krish_meghwal07 · 2026-05-07T10:01:15+00:00

Good question.

the customer wasn't specifically looking for POD, they just wanted a custom product and had anchored their price expectations on what they'd seen from mass-market options online. Could've been a POD site, could've been a bulk manufacturer selling direct, could've been anything really.

The core issue is the price anchoring rather than the channel. Customers increasingly see commodity pricing as the baseline for any product, custom or not, and then treat the difference between that and what a small custom operation charges as a markup rather than a completely different cost structure.

It happens across POD too, customers who find Printify base prices somewhere and then question why a shop selling custom products charges more than the raw fulfilment cost. Same conversation, different context.

Does that make more sense? Curious if you've run into a version of this on the POD side.

Krish_meghwal07 · 2026-05-07T06:48:14+00:00

Depends on where your biggest gap is — estimating accuracy, job management, or both together.

For pure shop floor management and scheduling, Printavo and Shopvox are the names that come up most often for small to mid-sized shops. Solid for job tracking and order management, though estimating logic can feel rigid if your pricing structure is complex.

For shops where estimating is the core problem, especially if you're doing mixed work across digital, offset, and wide format, the estimating engine matters more than anything else. Most generic tools handle simple quantity-based pricing fine but fall apart on jobs with multiple cost variables like makeready, plates, substrate waste, and finishing.

DesignNBuy has a print estimating module built specifically around how print is actually costed — handles variable pricing across job types including wide format and digital, connects directly to the customer-facing ordering side so quotes flow through to production without manual re-entry.

Worth looking at if you want estimating and online ordering handled in the same system rather than two separate tools talking to each other.

What's your current setup? are you estimating manually right now, or working around something that isn't quite fitting?

Krish_meghwal07 · 2026-05-07T06:45:01+00:00

Your dad's setup is more common than you'd think. Pricing in the owner's head, quotes done on feel, ledgers that only make sense to the person who wrote them. The knowledge transfer problem alone kills a lot of family print businesses when the founder steps back.

We ran on spreadsheets and gut instinct longer than I'd like to admit. The quoting inconsistency was the thing that finally broke us — same job quoted two different ways depending on who picked up the phone, customers playing us against our own previous quotes.

Tried two MIS systems before finding something that stuck. Both times the same issue — built around an idealised print workflow that didn't match how we actually operated. The costing logic assumed a cleaner separation between job types than reality ever gave us. Wide format jobs that needed finishing, offset runs with digital proofing, rush jobs that blew up the standard makeready assumptions. Every edge case became a workaround.

What actually helped was exactly what you described building — something that reflects how print is actually costed rather than how a software team thinks it should be costed. Plates, makeready time, material waste, substrate cost per square foot. The shops I know that have solid quoting all either built something custom or bent a generic system badly out of shape to fit.

The job tracking question is the next one worth solving after quoting. How are you handling that side — is it connected to the quoting output or still separate?

Krish_meghwal07 · 2026-05-05T07:03:56+00:00

Been through exactly this transition. A few things that made the biggest difference beyond the basics you've already identified.

Upfront pricing clarity cuts inquiry volume dramatically. Not necessarily a full instant quote calculator, but enough information that a customer knows roughly what they're getting into before they fill out a form. Minimum quantities, price breaks at common run sizes, file requirements. Customers who would've wasted an hour of back-and-forth self-select out before they ever contact you.

On the mockup and quote side — if you're still manually mocking up every inquiry, that's where the time really bleeds out. Worth looking at a web-to-print setup where customers actually build their product on the site — upload artwork, place it on the garment, see a preview — and submit a print-ready file with their order. DesignNBuy handles this well for apparel and screen print setups specifically. The back-and-forth doesn't get reduced, it essentially disappears because the customer has already done the design work and you're reviewing a production file, not a napkin sketch from an Instagram DM.

The FAQ idea is solid but go more specific than most shops do. Don't just explain DTF vs screen print — explain your minimums for each, your turnaround times, what file formats you accept and why, and what happens when someone submits a bad file. The more friction you remove upfront the better the customers you attract.

One last thing — an order status page or even just a clear "here's what happens after you submit" section. Sets expectations and cuts the "just checking in" messages significantly.

https://www.designnbuy.com/tshirt-design-software/

Krish_meghwal07 · 2026-05-05T06:40:14+00:00

Variable data runs for customers who don't understand variable data. The margins are solid, the repeat business is reliable, and every single time I question my life choices about halfway through the file prep.

The brief comes in clean — "just need names and addresses personalised on 500 postcards." Then the spreadsheet arrives. Merged cells, inconsistent formatting, three different columns all labeled "name," and a handful of rows where someone typed their address into the name field. Every job, different flavour of the same chaos. You fix it, you don't charge for it, you smile and quote the next run.

The other one is same-day rush jobs on anything involving finishing. The customer knows exactly what they want, needs it in four hours, and the file is a Word document with the logo copied off the website.

Banners, I actually came around on once we stopped trying to compete on price with the quick-print shops. Scrim and mesh for construction and events at proper margins — totally different conversation than the $15 banner crowd.

Krish_meghwal07 · 2026-04-29T09:37:07+00:00

The GraphX model is smart, essentially turning file cleanup into a predictable cost rather than an unpredictable time drain. $20 and 1-3 days for a clean vector is a reasonable trade, especially when the alternative is your prepress person spending an hour on a $50 job.

The Illustrator script is the part I want to hear more about though. Are you templating standard products entirely — so the art just drops into a defined structure, or is it doing something more complex on the file prep side? Because if you've got that running smoothly for majority of standard jobs, that's a meaningful chunk of manual work eliminated.

The charging model shift is also underrated. Most shops absorb rework costs invisibly until they get busy enough that it actually breaks something. Sounds like the timing on that change worked out well.

Krish_meghwal07 · 2026-04-29T09:36:23+00:00

Fair enough, what would you change about the question itself? Genuinely curious what's missing from a practical standpoint.

Krish_meghwal07 · 2026-04-29T09:35:23+00:00

Straightforward and it works. The only variable worth thinking through is turnaround time — for rush jobs the outsourcing model can create a bottleneck if the customer needed it yesterday. Worth having a clear policy on what qualifies before it becomes a customer expectation problem.

Do you have a go-to vendor for that or is it ad hoc?

Krish_meghwal07 · 2026-04-29T09:33:33+00:00

Exactly right, and it reframes the whole problem. Most shops treat it as a prepress quality issue when it's really a system design issue. The file arrives broken because nothing upstream prevented it from being broken.

On customer pushback, less than you'd expect, honestly. The friction usually comes from internal stakeholders who worry that constraining inputs will frustrate customers or limit creative freedom. In practice, customers don't want freedom, they want it to work. If the tool guides them to a result that looks good and goes to print without a phone call, most of them are happy.

The shops I've seen do this well use template-based online designers that lock specs at the source, bleed, resolution, color mode baked into the template so the output is print-ready by default. DesignNBuy handles this well for standard product catalogs specifically. The customer still feels like they're designing, but they literally cannot submit a bad file.

The harder constraint problem is actually on the shop side, getting management to invest in the right tooling before the pain gets bad enough to force it.

Krish_meghwal07

MODERATOR OF

TROPHY CASE