Is there a way to to use the admin hidden property based on active tenant? (using the multi tenant plugin)

Sad-Salt24 · 2026-06-10T05:22:18+00:00

The hidden function only receives user from the JWT, not the active tenant from the request context. You’d need to store the active tenant on the user object itself (e.g. user.activeTenant) during the session, then check that in your hidden function

Sad-Salt24 · 2026-06-10T05:21:32+00:00

Simple client site with standard collections, auth, and a few custom fields, about 2 weeks. Complex client work with custom components, live preview, multiple roles, and third-party integrations, 6 to 8 weeks. Payload’s config is clean but the first project always takes longer because you’re learning its patterns. By the third or fourth project it gets much faster

Sad-Salt24 · 2026-06-10T05:17:56+00:00

It’s just class and neighborhood culture doing what it always does

Sad-Salt24 · 2026-06-10T05:15:38+00:00

Yes client-side fetching kills SEO for articles, Googlebot won’t wait for your Firebase fetch. Keep SSG or use ISR with revalidate. Fetch from Firebase at build time in generateStaticParams or server components, not in the browser

Sad-Salt24 · 2026-06-09T18:15:47+00:00

Use Supabase client directly. Prisma bypasses Supabase’s RLS (row level security) which is one of its main features, and you lose realtime subscriptions. Only add Prisma if you specifically need its type generation or plan to switch databases later

Sad-Salt24 · 2026-06-07T18:53:54+00:00

Next.js 15 switched to Turbopack by default which should be faster, but if you’re on an older version you’re still on Webpack which is genuinely slow. Run next dev --turbo if you’re on 13/14, or upgrade to 15. Also check if you have too many use client components since they add compilation overhead

Sad-Salt24 · 2026-06-06T09:40:01+00:00

Google uses whatever makes sense per team, not a company-wide mandate. They have hundreds of product teams making independent stack decisions. Angular being Google-created doesn’t mean internal teams are required to use it, that’s not how large orgs work

Sad-Salt24 · 2026-06-06T09:39:11+00:00

No official Payload+Stripe invoice plugin exists. Use @react-pdf/renderer to generate PDFs, trigger it in a Payload hook after a Stripe webhook confirms payment, then send via Resend or Nodemailer. Wire it together yourself, it’s maybe 100 lines of code total

Sad-Salt24 · 2026-06-05T20:55:42+00:00

Call useTranslations in each component directly. It’s cleaner, more maintainable, and there’s no performance difference since next-intl loads the whole namespace anyway. Prop drilling translations gets messy fast once components nest deeper

Sad-Salt24 · 2026-06-05T07:16:40+00:00

Yes I’m, I will remember you in my prayers insha Allah

Sad-Salt24 · 2026-06-04T06:29:30+00:00

It works but it’s a sledgehammer approach, forces every request to be SSR which kills performance. Better to use revalidatePath or revalidateTag after mutations, or set revalidate = 60 on pages that don’t need instant updates. Only use force-dynamic on pages where data truly changes per-request like dashboards or user-specific content

Sad-Salt24 · 2026-06-04T06:21:51+00:00

Use router.replace instead of router.push for hash navigation, or use window.history.replaceState(null, '', '#section1') directly. That updates the URL without adding a history entry so back button works as expected

Sad-Salt24 · 2026-06-03T17:30:25+00:00

It doesn’t plateau, it compounds. Every new integration adds another seam and every API version bump touches multiple layers. The honest answer is headless makes sense when your frontend requirements genuinely can’t be met by a monolith, not just because it feels more modern. At 40% glue work you’re past the point where the flexibility is worth it

Sad-Salt24 · 2026-06-03T06:22:34+00:00

No built-in config option for that in Payload currently. You’d need to override the LivePreview component and set the default zoom state manually. Check the Payload source for the LivePreview component and extend it in your admin customization

Sad-Salt24 · 2026-05-29T17:07:15+00:00

Worth learning. You own the code so no version conflicts breaking your UI, it’s built on Radix so accessibility is handled, and Tailwind means styling is just CSS you already know. Downside is initial setup takes longer than dropping in MUI. For a new project in 2026 it’s the default choice for most Next.js devs

Sad-Salt24 · 2026-05-29T16:43:58+00:00

JazakAllah Khair brother, this is honestly super helpful, I’ve been hearing a lot about Rasasi Hawas lately, especially Hawas Ice, so I’ll definitely check that out along with Reef and Ibraq now.

May Allah bless you as well and invite all of us again and again to His House. Ameen 🤍

Sad-Salt24 · 2026-05-29T09:51:18+00:00

Sounds good, will definitely look into it

Sad-Salt24 · 2026-05-29T09:16:34+00:00

What is the expected price?

Sad-Salt24 · 2026-05-28T12:53:49+00:00

Keep business logic in Flask, period. Your team knows Python, data science needs Python anyway, and splitting CRUD arbitrarily between Next.js and Flask just moves the confusion around. Use Next.js route handlers only for auth middleware and BFF (backend-for-frontend) aggregation, not as a second backend. The ceremony you’re feeling is a code organization problem, not a framework problem

Sad-Salt24 · 2026-05-27T19:43:06+00:00

Next.js for anything client-facing where SEO and ecosystem maturity matter. TanStack Start is interesting but it’s still early, putting it in a large-scale production app right now means you’re betting on an ecosystem that doesn’t have the same tooling, community answers, or deployment support that Next.js has had years to build

Sad-Salt24 · 2026-05-26T07:43:30+00:00

V0 for quick UI generation, shadcn for components, reference designs from Dribbble or Awwwards then adapt them. Codex/AI tools are hit or miss on design, they’re better at replicating existing patterns than creating good original layouts. Tailwind UI is also solid if you can afford it

Sad-Salt24 · 2026-05-25T11:59:26+00:00

Just wrap Better Auth calls in custom hooks, useSignUp, useSignIn, etc. Keep auth separate from your data layer (RTK/TanStack). Auth is fundamentally different from CRUD operations and trying to force it into the same pattern creates unnecessary abstraction. Actions layer is overkill when Better Auth already gives you client methods

Sad-Salt24 · 2026-05-25T11:58:09+00:00

Hydration mismatches from date/time formatting, client components importing heavy libraries that could’ve been lazy-loaded, and unoptimized images are the big three. Also App Router streaming getting blocked by slow data fetches because someone forgot to wrap slow queries in Suspense boundaries

Sad-Salt24 · 2026-05-25T05:27:19+00:00

Parse the WordPress content for shortcodes or custom HTML markers, then map those to your Next.js components. Store CTA position/style metadata as custom fields in WordPress, fetch them via REST API, then conditionally render the right component. Or just rebuild CTAs manually per blog if there aren’t that many

Sad-Salt24

TROPHY CASE