BaseHub like solution to frictionless On-Demand Revalidation (Pump)

[JarvisPrestidge]

Hey love a lot of things about payload, but not so much the complexity of wiring up all the necessary parts to get live preview, on-demand revalidation and caching working in a frictionless way (perhaps i'm missing something in the docs, but I can only find 1 blog post about on demand revalidation for example and nothing about caching).

I took a look at BaseHub recently via the Next-Forge vercel production starter repo as it's the recommended baked in CMS solution, and I can kind of see why, it gets out the way, and defaults to having revalidation handled by using a <Pump> server component, very low config / code complexity to get this working, no fine grain hooks etc.

Just wondered if anyone from Payload has had their eyes on this, because for me Payload is all but perfect, with just some dev experience / missing docs around how to optimize a deployment (let's say on vercel) to correctly implement on-demand revalidation and specifically caching (so we're not burnt with hosting fees).

I suppose the take away of this feature request would be:

• New docs on:
  • On-Demand Revalidation
  • Caching optimisations
• Consider an ergonomic server component like BaseHubs <Pump> to abstract some of this complexity/friction.

Reading:

https://basehub.com/blog/pump

[paulpopus]

I don't think the Pump component handles on demand revalidation per se, but it will handle the live previews and queries for you. We don't yet have an SDK but that's planned which could automatically take care of caching data for you.

However we do have a pretty simple pattern for live preview with react, on our website template we have a custom component that just imports our listener and then conditionally render it.
This enables you to have server side live preview as well as setup there.

Appreciate the feedback! I think the SDK will help a lot here for sure especially with caching but in the meantime we'll work on a tutorial around this